Bug#856570: apache2: does not send any Content-Type for plaintext files

2017-03-03 Thread Thorsten Glaser
On Fri, 3 Mar 2017, Dominik George wrote: > Apache uses /etc/mime.types to translate extensions into mime types, > which, in my eyes, is a design flaw, because it is a 1:n mapping used by I believe this system to be horridly flawed anyway… I mean, where should Apache know the correct MIME type fr

Bug#856570: apache2: does not send any Content-Type for plaintext files

2017-03-03 Thread Dominik George
> As “no extension” is mapped in mime.types to many > mime types (mind you: not to *no* mime type), the > DefaultType doesn't kick in. Nor does mod_mime_magic, which is probably the real bug here. mod_mime_magic should probably be used to disambiguate in case of doubt. -nik -- PGP-Fingerprint:

Processed: retitle 856570 to apache2: does not send any Content-Type for files without extension

2017-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 856570 apache2: does not send any Content-Type for files without > extension Bug #856570 [apache2] apache2: does not send any Content-Type for plaintext files Changed Bug title to 'apache2: does not send any Content-Type for files withou

Bug#856570: apache2: does not send any Content-Type for plaintext files

2017-03-03 Thread Dominik George
> Apache 2 does not send *any* Content-Type header for plaintext files > any more, so I cannot tell it to send “text/plain; charset="UTF-8"” > to work around at least TWO bugs in Firefox (which likes to interpret > those files, unlike Lynx, Chromium and Safari, as windows-1252). This is not entire