httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 13986] - remove default MIME-type
Date Sat, 26 Oct 2002 23:13:12 GMT
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 bzbarsky@mit.edu  2002-10-26 23:13 -------
This is based on a few hours of looking at the code and zero prior knowledge of
it.  So I strongly suspect that the details are not quite up to snuff.  But the
general idea is pretty simple...  Note that the changes only kick in if there is
no DefaultType directive.  If people are OK with these changes, changing the
default httpd.conf would be pretty simple...

There are two spots (marked with XXX comments in the patch) where I was _really_
not sure what the right thing to do was.  Also, I changed the multipart code to
not send a content-type for a subpart if one is not set, but it may be a better
idea to default that to application/octet-stream instead.  I'm not sure which
RFC is most relevant there and what sorts of problems that change could cause.

On another note, how is UA support for HTTP X where X > 0.9 responses with no
content-type set?  Is this a feasible approach in general?

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


Mime
View raw message