Many packages gzip their README files, and even (often) their examples.  It saves
space, and it quite useful to me as a user, since I can (usually) just open it normally
(I have lesspipe installed).

However, DWWW wanted to download the Gziped readme.md I pointed it to.  Is there
any way that can be changed, so that it gets decompressed and then served?

For that matter, I would be intrested in seeing more flexibility in serving files.
For instance, .gz extensions could be decompressed, .md fed through kramdown (if
its installed), ect.  Even if there was just a way to define filters (if the following
files are accessed, send them through these programs first), usability would improve immensly.

Thanks!
Calum

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dwww depends on:
ii  apache2 [httpd-cgi]    2.4.46-1
ii  debconf [debconf-2.0]  1.5.74
ii  debianutils            4.11.2
ii  doc-base               0.10.9
ii  file                   1:5.38-5
ii  libc6                  2.31-4
ii  libfile-ncopy-perl     0.36-2
ii  libmime-types-perl     2.17-1
ii  man-db                 2.9.3-2
ii  mime-support           3.64
ii  perl                   5.30.3-4
ii  sensible-utils         0.0.12+nmu1
ii  ucf                    3.0043

Versions of packages dwww recommends:
ii  apache2 [httpd]  2.4.46-1
ii  apt              2.1.10
ii  dlocate          1.07+nmu1
ii  info2www         1.2.2.9-24
ii  swish++          6.1.5-5

Versions of packages dwww suggests:
ii  chromium [www-browser]     83.0.4103.116-3.1
ii  doc-debian                 6.4
ii  dpkg-www                   2.60
ii  firefox-esr [www-browser]  78.3.0esr-2
ii  lynx [www-browser]         2.9.0dev.6-1
ii  w3m [www-browser]          0.5.3-38+b1

- -- debconf information:
  dwww/badport:
  dwww/cgiuser: www-data
  dwww/serverport: 80
  dwww/index_docs: false
  dwww/nosuchuser:
  dwww/cgidir: /usr/lib/cgi-bin
  dwww/nosuchdir:
  dwww/docrootdir: /var/www
  dwww/servername: CalumsBeastlyLaptop.computercalum.com
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl+ZrecdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzIyKxAAgGsJRU+v6zu3oMiY
q2aLYVkvWuRtRXksrOLew6LFbL+bZMoOhYq4J4BWEy+7EPsnHsooi7HStfDF3eEb
SoJYcr3mM/g7GOiBEemxMgQeleoH+v1WQD6TtEFBNgClg30Kchwq66AzisoZ3m9R
ZB+irSaT/VZgYvTFYHikPw6qOcsXvS5FN13e5LTI+2FeghcplF6uD69BHm1cjI07
eb1l7iPxRRvmnh7YDl42EuMy+2TFVSOQZ54nYqbwrqIqturSS5tXlSEitlTPEX5p
0o9635UCHYkimw967nimK4uNOYB0/MMfpA8vYoNVji/u3u0Qt5iGLhvFasFm6VYZ
PpWRXXV370RjyolJBUeYRWFXUAU6r8X5wMOZaE2I+JpXYtyWUqr8+MRVm0GC0ql0
QYvc+r2Ifoz9760bwt2ljtkXtO24huukYcuLGwJRONpX4x0RN8puaosRHsF6DXxe
zPAbLbA4WcQnKMhnlg4jGU5DENflvV7C1HoxyIMXS4dL3rNJEdkpyhQEL9RR5U62
oA/BC85esTAqR381Rh/YXvpHP/AR5SyBkwAxRvdcpZM0XTHDtl9ArqsViP/D9na0
uzOsuRhzbnverNvfuNLT4TRfwvj3HfPTqfmeXhFzRxcK8eE0rUaAIjD2JoTuQbrL
bRK5EcrBjVyRqukCUK2QS2+RS8o=
=xGLe
-----END PGP SIGNATURE-----

Calum McConnell writes:

The issue is related to files in a markdown format only, so I've
retitled the bug already. I'll add a work-around for it in next dwww
upload to treat markdown files as plain text files

They are already. However the markdown file was sent as 'text/markdown',
and your browser did not know how to handle it.

I'll work on providing better support next year.

Regards,
Robert