Nick Kew <nick <at> webthing.com> writes: > libxml2 uses utf-8 internally and transcodes on input, so mod_proxy_html > determines encoding and tells libxml2. To re-transcode on output would > be an additional overhead, which mod_proxy_html doesn't incur. Since > transcoding filters (like mod_charset_lite) are available, it would be > superfluous for mod_proxy_html to do that too. > > You could insert a transcoding filter after mod_proxy_html to get back > your iso-8859-1. Or you insert a transcoding input filter when you > accept the form data. > Thank you for this precious hint! As far as you know, in this way i can determine the original encoding of the webserver to reencode everything as it was? I will have to integrate several apps and cannot ensure that the encoding they will use is the same for all. Best regards, Jens --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|