-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joseph,
On 3/19/2009 7:49 PM, Joseph Millet wrote: > Maybe I'm missing something but from the little knowledge I have, I'd > think an HTML form is posted encoded in the form enclosing HTML > document charset specified in the sent Server headers. It doesn't really matter what the client decides to do (they can submit in a different charset for all I care) as long as it indicates in the request headers what the charset is. The problem is that many clients do /not/ indicate the charset in the request, even though the spec requires them to do so. If the above assertion generally holds (POST charset matches the form's enclosing document's charset) you can't bet on it. > So that you settle a page encoded in iso-8859-2, you wouldn't expect > a form present in that page to post unicode data, would you ? As I said, it's only a coincidence that the client sends the POST data in a matching charset. The only surprise is that the client sends something other than ISO-8859-1 (the default as per the spec) but does not tell the server what it is. :( - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknDCl0ACgkQ9CaO5/Lv0PDLPwCffJMY3m0yySjboyKFHt1ENFdG EzgAnjr9/6KXxhQFaBKc1xE/HSbCez7R =87hJ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
