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-05 11:25 ------- But Apache _does_ know what he sends, because he was configured so. I have to disagree here. Apache doesn't know what it is sending, it just sending what someone told it. That's is not the same! I'm sure they didn't thought of it like that when writing the HTTP-specs. Setting the DefaultType to octet-stream by default goes against the RFC-specs, this is a decision for the client, not the server. The reason for it is problably when the client knows some unofficial/propriety MIME-types, unknown to Apache. Apache would send for instance a Mimi-Type of text/plain (current) or octet-stream. The client is not allowed to verify this (see HTTP-specs) and thus have to display the content as text or saving it as a file as bytes. But this may not be what the author intended. My suggestion would be that either the defaultype is removed or set to None (by default). But, why does the DefaultType exists anyway? It is not correct by RFC (in most cases), it just a practicallity. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
