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 23692] - mod_proxy alters Content-Type breaking google+mozilla
Date Wed, 24 Mar 2004 21:38:32 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=23692>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=23692

mod_proxy alters Content-Type breaking google+mozilla





------- Additional Comments From P@draigBrady.com  2004-03-24 21:38 -------
Ok I think this is quite serious (at least for mozilla/opera
which are correctly honouring the Content-Type in the HTTP-header).
At first I thought it was a mozilla bug:
http://bugzilla.mozilla.org/show_bug.cgi?id=238488
In there is referenced http://www.cert.org/tech_tips/malicious_code_mitigation.html
which to me suggests that if apache is setting the DefaultCharset
it should translate characters as appropriate.

Personally I think what apache should do is to inspect
the charset=value in the file and set the HTTP-header to match
iff AddDefaultCharset is set.

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


Mime
View raw message