On Fri, 16 Nov 2012 11:31:38 +0100 Thomas Eckert <Thomas.Eckert@xxxxxxxxxx> wrote: > Thanks for the hint but unfortunately "manually" adding xml2enc to the > filtering chain does not help. Looks like you've got problems over and above anything to do with your configuration! > "SetOutputFilter INFLATE;proxy-html" gets the page displayed correctly I thought you said it had charset issues? > [pid 15039:tid 3007834992] mod_xml2enc.c(259): [client > 10.10.10.10:40388] AH01434: Charset ISO-8859-1 not supported by libxml2; > trying apr_xlate That seems implausible. How do you get a libxml2 install that doesn't natively support ISO-8859-1 (latin1)? > [pid 15039:tid 3007834992] mod_xml2enc.c(490): (22)Invalid argument: > [client 10.10.10.10:40388] AH01441: xml2enc: converted 1/1 bytes > [pid 15039:tid 3007834992] [client 10.10.10.10:40388] AH01444: Skipping > invalid byte(s) in input stream! > (and more conversion errors) It looks as if your backend incorrectly identifies the charset of the page in question. Either that or you found a bug. Do you have a URL where your unprocessed page could be viewed? -- Nick Kew --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|