Joseph Millet wrote:
Thing is you've got an HTML form that you tell browsers it is
ISO-8859-2, so when they post it to form target URL - it gets send
encoded as ISO-8859-2, it is then your responsibility to parse
incoming queries
Sorry, but I think this is incorrect.
According to the HTTP specs, the client should specify a character
encoding, and the server should respect the specified character encoding
indicated by the client, and not guess.
...
> in the encoding you asked it to be encoded.
How does the server ask the client to encode his request ?
Depending upon your requirements, UTF-8 will fit most of any languages
needs
True, but irrelevant here until the HTTP specs are revised.
There is one confusing case : a GET request, with the parameters encoded
in the URL, because in that case the client has no defined way to
specify the real character encoding of the request parameters.
That is a shortcoming of the HTTP and URL specs.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
