Re: [us...@httpd] using ProxyHTMLEnable On, mod_proxy_html or xml2enc segfaults

2009-11-09 Thread Martin Gerdes
You solved it! :-) We have still to test the webapp in its entirety, but it doesn't crash where it crashed before, AND correctly translates encodings :-) Thanks a lot for your helpfulness, and the new version! 2009/10/30 Nick Kew > Martin Gerdes wrote: > >> Cool. Then I'll cease trying to buil

Re: [us...@httpd] using ProxyHTMLEnable On, mod_proxy_html or xml2enc segfaults

2009-10-30 Thread Nick Kew
Martin Gerdes wrote: Cool. Then I'll cease trying to build a test case for now. That would probably have cost me another day... I think I've solved it. Well, I've found and fixed a bug that your response would be likely to provoke. I hope that fixes it! http://bahumbug.wordpress.com/2009/10/

Re: [us...@httpd] using ProxyHTMLEnable On, mod_proxy_html or xml2enc segfaults

2009-10-30 Thread Martin Gerdes
Cool. Then I'll cease trying to build a test case for now. That would probably have cost me another day... Small correction of the problem description: I mistakingly wrote that the login page was served in utf8. This is incorrect: It was correctly translated to ISO-8859-1 :-). So if you manage to f

Re: [us...@httpd] using ProxyHTMLEnable On, mod_proxy_html or xml2enc segfaults

2009-10-29 Thread Nick Kew
On 29 Oct 2009, at 14:00, Martin Gerdes wrote: Allright, I will try. Stuff I can tell you immediately: The packet that causes the crash looks like this (sniffed with tcpdump): HTTP/1.1 302 Moved Temporarily Server: Apache-Coyote/1.1 Location: http://localhost:50100/dwhfe/app/start/StartP

Re: [us...@httpd] using ProxyHTMLEnable On, mod_proxy_html or xml2enc segfaults

2009-10-29 Thread Martin Gerdes
Still have not managed to simplify it. I have managed to set up a simple proxy using a virtual host, but I have yet to figure out how to fake those http options. Interestingly, I could get a simple sample page translated back into ISO-8859-1 in this setup. This at least tells me that my self build

Re: [us...@httpd] using ProxyHTMLEnable On, mod_proxy_html or xml2enc segfaults

2009-10-29 Thread Martin Gerdes
Allright, I will try. Stuff I can tell you immediately: The packet that causes the crash looks like this (sniffed with tcpdump): HTTP/1.1 302 Moved Temporarily Server: Apache-Coyote/1.1 Location: http://localhost:50100/dwhfe/app/start/StartPageSelector.htm;jsessionid=B6B4331C1C0C14A7BE964B89E1E7

Re: [us...@httpd] using ProxyHTMLEnable On, mod_proxy_html or xml2enc segfaults

2009-10-29 Thread Nick Kew
Martin Gerdes wrote: I can load the login page of the webapp, though it is returned in utf8. Once I send of the login data, it segfaults. It did NOT do that when I used SetOutputFilter instead of ProxyHTMLEnable, so I assume that xml2enc crashes, though that is only conjecture. Line in apach

[us...@httpd] using ProxyHTMLEnable On, mod_proxy_html or xml2enc segfaults

2009-10-29 Thread Martin Gerdes
2009/10/29 Nick Kew > > 2009/10/28 Martin Gerdes > >> Background: >> I am running Apache as provided for Debian Lenny (2.2.9-10+lenny4) as >> a reverse proxy. To that end, I installed libapache2-mod-proxy-html >> (3.0.0-1) for URL rewriting. >> As the original content is in charset ISO-8859-1, I