Alright, xml2enc works, does not crash, and correctly translates UTF8 back
to ISO-8859-1 after it was converted to UTF-8 by mod_proxy_html.
However, activating that translation back to ISO-8859-1 makes the whole
process take up a lot of time, and I have no idea why, so I am asking for
ideas.
On 10 Nov 2009, at 08:56, Martin Gerdes wrote:
First, how slow is slow? Time from pushing the send button until the new
webpage is loaded rises from 10.6 to 103 seconds.
10.6 is already horrendously slow (unless perhaps it's a 20-year-old PC),
which leads me to wonder what you're doing
Can you get mod_diagnostics
output to track the data running through the filter?
I'll try that after lunch. Ask if you want to know anything else. (I can
for example packet sniff the connection between IE and the proxy, and give
you the debug output of mod_proxy_html in that
A completely different idea to solve my actual problem:
Someone else suggested to just take out the conversions all together.
I mean, I am converting right back into the encoding I converted from. I
have been assured that no link uses a character above the first 128 (7 bit
ASCII). As far as I
to the regularly scheduled
program...
2009/11/10 Martin Gerdes marting...@googlemail.com
A completely different idea to solve my actual problem:
Someone else suggested to just take out the conversions all together.
I mean, I am converting right back into the encoding I converted from. I
have been
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 n...@webthing.com
Martin Gerdes wrote:
Cool. Then I'll cease
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
/, and contains /usr/lib/libxml2.so), but I will try to
get those symbols defined. Hopefully that will do it.
All help and suggestions appreciated.
Martin
2009/10/28 Martin Gerdes marting...@googlemail.com
Background:
I am running Apache as provided for Debian Lenny (2.2.9-10+lenny4) as
a reverse proxy
2009/10/29 Nick Kew n...@webthing.com
2009/10/28 Martin Gerdes marting...@googlemail.com
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
on, and loglevel info.
Will now test whether I can put the same content into a static website
getting the same crash...
2009/10/29 Nick Kew n...@webthing.com
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
send
[Thu Oct 29 16:07:15 2009] [notice] child pid 4210 exit signal Segmentation
fault (11)
I'll continue to try to build a simple test case, but I have to figure a bit
more stuff out for that...
2009/10/29 Martin Gerdes marting...@googlemail.com
Allright, I will try.
Stuff I can tell you
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 set the option
ProxyHTMLCharsetOut * to get the webpage output as
12 matches
Mail list logo
