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 Jan 2004 23:00:56 -0000
Message-ID: <20040105230056.12561.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 14095]  -
    Change default Content-Type (DefaultType) in default config

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

bzbarsky@mit.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erik@codefaktor.de
             Status|CLOSED                      |REOPENED
         Resolution|DUPLICATE                   |


------- Additional Comments From bzbarsky@mit.edu  2004-01-05 23:00 -------
Erik, I'm sorry, but I have to reopen this.  The other bug is rather difficult
to resolve, involving changes in core architecture and such (see the objections
raised to my proposed patch).  It's not likely to be a change that happens in a
minor point release.

This bug is requesting a one-line change in the default config file that can be
made by anyone who can type.  It could happen in a maintenance release, imo...
(and should have happened by now if the Apache group is at all interested in
trying to resolve the browser makers' concerns about this behavior).

To be truthful, I am _very_ close to just hardcoding a check for the Apache
server in Mozilla and just ignoring any type sent by such servers, since it's
clearly bogus so much of the time.  Our built-in content-sniffing would do a
better job.  It pains me to say this, but IIS has the right behavior here; I
can't figure out why the Apache group is so set on screwing over people trying
to write browsers complying with the HTTP standards.

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