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 00:37 ------- André, I realize that you just distribute a sample config. Too bad most people just use it without modifying it... The reason your config affects browser compliance is that IE ignores the type you send. That means that all other browsers look "broken" when they follow the HTTP, since IE clearly "works" (does what the person serving the page wanted it to do). This means that other browsers either have to fail on many real-world pages or break the HTTP spec; in practice they are starting to choose the latter at this point. I've been pretty calm for over a year now (ever since bug 13986 got filed and I attempted to start a thread on the issue on the dev list only to be completely ignored). In that time, I have had to deal with dozens of Mozilla bug reports requesting that we simply ignore the type because of Apache's default config (I am not counting the hundreds of bug reports filed in the same period of time that got reassigned to evangelism to contact the site and ask them to pretty please make the change that this bug requests be made in the default config). It's hard to be calm when so much of my time is being wasted on this issue, which is why I am considering explicitly checking for Apache at this point -- it would simply save me enormous amounts of time, especially if there are no plans to address either this bug or bug 13986. Erik, as I pointed out the default setup of IIS is to send application/octet-stream as the "unknown data" type. There would be no problem in the reverse direction, because as soon as Apache started sending application/octet-stream people who fail to configure their servers would see their pages "break" in IE AND WOULD FIX THEIR SETUPS. Which is what we all want. It's unfortunate that the MIME bugs in IE make the text/plain behavior acceptable because, on average, the users simply don't notice it. Changing to a type they _do_ notice would have very beneficial consequences, imo. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
