You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/06/07 00:12:30 UTC
DO NOT REPLY [Bug 9678] New: -
UTF-8 pages are being transcoded so that old browsers break.
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=9678>.
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=9678
UTF-8 pages are being transcoded so that old browsers break.
Summary: UTF-8 pages are being transcoded so that old browsers
break.
Product: Apache httpd-1.3
Version: 1.3.24
Platform: Other
OS/Version: Linux
Status: NEW
Severity: Major
Priority: Other
Component: mod_proxy
AssignedTo: bugs@httpd.apache.org
ReportedBy: martin@cwa.co.nz
After upgrading our reverse proxy to 1.3.24 (from 1.3.20) we found that the
following clients:
- lynx (tested 2.8.3rel.1)
- netscape 4.7x and 3.x (mac and win)
- IE 6 (unconfirmed)
find random char sequences inserted in the html. The char sequences are 3
characters long ("ee4", "eb3"). We believe this to be an issue with the HTTP
libraries at the client side getting confused with the UTF8 encoded stream.
All our pages are being sent with "Content-Type: text/html; charset=utf-8"
Many clients work properly:
- IE 4,5,6 (although we have some unconformed reports from users of IE6 that
were behind a squid proxy)
- Mozilla 1.0RC1 1.0RC2 (mac/win/linux)
- Perl's LWP libraries (this problem has fooled GET, our favourite HTTP
debugging tool).
Downgrading to 1.3.20 solves the issue.
We have been able to reproduce it just with
- ProxyPass
- ProxypassReverse
so it does not seem to be related to particular settings.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org