I run into a problem when trying to use mod_proxy_html 3.1.2, although it was on an old Centos system and not a Debian, I still think it worth mentioning here.
The problem seemed to be that mod_proxy_html uses mod_xml2enc to decide which encoding the page has. This is supposed to look at the HTTP headers first, and then at a meta tag. But in practice it seemed to ignore the charset in the HTTP headers, defaulting to iso-8859-1, and thus double- encoding characters that were already in utf-8. As far as I could see, the xml2enc module init fails somehow (EAGAIN), and the module does not really get used. Unfortunately I didn't have the time to dig to the bottom of this issue, when I found that Debian still uses 3.0.1, I switched to that, and things worked - at least as long as there is a charset definition in the HTTP Content-Type header. I just made sure it was there. -- Heikki Levanto heikki at indexdata dot dk "In Murphy We Turst" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
