Patrick Gansterer 387e50bd8f Allow serving files without known mimetype ... RFC2616 only says that any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field defining the media type of that body. RFC2119 defines SHOULD as: This word mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. AG: this isn't an oversight, it's paranoia about sending out /etc/passwd or /etc/shadow accidentally. I agree it should be allowed if people really want to override it. But the default should remain like it is I think. I adapted the patch to allow the extra mimetype "*": "" to be declared on a mount, as a wildcard match that serves the file without a Content-Type.		2016-08-14 19:28:29 +08:00
..
html	Allow serving files without known mimetype	2016-08-14 19:28:29 +08:00