Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
Date: 5 Feb 2003 16:04:26 -0000
Message-ID: <20030205160426.13689.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 13986]  -
    remove default MIME-type

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=13986>.
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=13986

remove default MIME-type


------- Additional Comments From kaldari@monsterlabs.com  2003-02-05 16:04 -------
Let's try that again (somehow my linebreaks got stripped)...

> The Apache doesn't exist only for Mozilla. What about the thousands of
> browsers out there? How do they work without getting a content type?

Most other browsers (like IE) work by violating RFC 2616. This is also why
sysadmins can generally get away with being lazy about setting their MIME types.
Most users will never know the difference. The problem here is Mozilla is
bending over backwards to try NOT to violate RFC 2616. But unless we can get
some cooperation from Apache, Mozilla too will have to violate the spec.
Chimera, Mozilla's Mac OS Browser, already does. They tried the evangelism route
and it was like trying to bail a sinking ship with a teaspoon. The practical
reality is that unless Apache removes the default MIME type or implements some
kind or null default (as I believe the RFC intended) Mozilla will have to do
MIME sniffing in some situations (or forget about trying to be a usable browser).

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org