Bug#856570: apache2: does not send any Content-Type for plaintext files
On Thursday, 2 March 2017 16:15:45 CET Thorsten Glaser wrote:
> Apache 2 does not send *any* Content-Type header for plaintext files
> any more,
With "any more", do you mean that this is a regression, i.e. did it work in an
earlier version? If yes, which version?
On Friday, 3 March 2017 12:28:17 CET Thorsten Glaser wrote:
> 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 from?
If the defaults don't suite you, you have to configure the mime types manually.
In general, no Content-Type header is much better than a wrong Content-Type
header. So, not having any default for no file extension seems reasonable.
> A system based on a registry (mapping files to MIME types in a
> database; entry is automatic with a guessed type if none exists
> but can be overridden) is better.
You may want to look at libapache2-mod-mime-xattr
Reply to: