On Mon, Mar 16, 2009 at 3:10 PM, Mikolaj Rydzewski <m...@ceti.pl> wrote: > > It doesn't work for me. By default Tomcat uses ISO-8859-1 encoding. And it > will try this encoding to parse input parameters. >
That's true, I'm doing the same here for German Umlaute, however: One link in the Wiki is pointing to HTTP specification section 3.4.1, however, there's something that I do not understand: The specs say in 3.4.1: <quote> HTTP/1.1 recipients MUST respect the charset label provided by the sender; and those user agents that have a provision to "guess" a charset MUST use the charset from the content-type field if they support that charset, rather than the recipient's preference, when initially displaying a document. See section 3.7.1. </quote> So, for me as a non-native English speaker, I understand it in such a way that your conent-encoding must be obliged - or do I get it wrong here? So, if in the content-encoding UTF-8 is specified, why isn't it accepted then? Rgds Gregor -- just because your paranoid, doesn't mean they're not after you... gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
