On Fri, Apr 19, 2002 at 02:48:17PM +0200, Marco Marongiu wrote: > Hello again > > I'm becoming convinced that AxKit 1.5 doesn't love me, indeed. :-] > > I had another problem today. All AxKit pages in a web site showed > strange character strings on top and bottom. For example, the main page > had a string "c67\n" before the <html> tag and "\n0\n\n" on bottom (\n > was a real newline, not a literal backslash followed by n). That showed > up on Netscape 4, lynx and a few browsers, while it was ok on Mozilla. > > There were also other odd facts about that: connecting to the front-end > proxy with Netscape 4 showed the problem, while it didn't on the > back-end AxKit server. Telnetting on both showed the problem anyway. > > The problem vanished as soon as I commented the lines: > > # AxOutputCharset iso-8859-1 > # AxTranslateOutput On > > What was wrong about that? I guess that something went messed up with > the character set on the way browser<->proxy<->axkit, but I can't guess > exactly what... I also remeber that the use of those directive was more > or less discouraged, but it didn't result in any problem before today...
This is due to the dechunking problems in mod_proxy. They are fixed in apache-1.3 cvs. See the apache-httpd-dev, and apache-modperl lists for details. http://marc.theaimsgroup.com/?l=apache-httpd-dev http://marc.theaimsgroup.com/?l=apache-modperl Ed --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
