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 [EMAIL PROTECTED] 2003-02-04 15:49 ------- If I understand the HTTP/1.1-RFC correctly, Apache MUST NOT send an Content- Type header if it does not know what it is sending. If they would have wanted that, they would have used the word MUST. They used the word should to make clear that the webserver should make every effort to send an correct and appropriate Content-Type header. Sending a header of text/plain in cases that the content-type is unknown goes against what the HTTP-specs say. If the server doesn't know, perhaps the client will (should sniff the content an/or extensions). And if it doesn't, then it should tread it as application/octet-stream. This decision lies with the client, not the server. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
