DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14095>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14095 Change default Content-Type (DefaultType) in default config ------- Additional Comments From [EMAIL PROTECTED] 2004-01-06 21:00 ------- As I pointed out in bug 25650, the underlying problem is configuration, not any bug in the server. Apache expects users to configure mime types. The problems here are: 1. Users who don't configure mime types correctly; and 2. MSIE, which created an expectation that incorrect configurations work. This is not only wrong, it is also a security problem. Individually, neither of these problems would be a big deal. Together, they create an issue that we probably should address. One thing to think about, Andre: DefaultType actually serves two purposes. 1. It determines the type for files with unmatched extensions. 2. It determines the type for files with NO extensions. Files of the second type are quite likely to be text/plain (think README, etc), which is probably why that is currently the default. And Apache provides no easy way to set the type of these files other than DefaultType. But given the balance of harm, it is probably still a good idea both to change the DefeaultType, and to allow for no Content-Type. Everyone should be aware, however, that this won't magically fix all the broken servers out there. Servers with this type of problem are also the ones that are least likely to have an admin that will carefully inspect changes in default config files. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
