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. 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 ?
On Tue, Mar 17, 2009 at 2:31 PM, Christopher Schultz <ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Pid, > > On 3/17/2009 6:52 AM, Pid wrote: >> Does the Servlet Spec define the default value of the request encoding, >> or is this a Tomcat feature? > > The servlet spec (section 3.9 "Request data encoding") specifies > ISO-8859-1 as the default encoding for POST data when no charset has > been specified. Although the servlet spec provides a default, I believe > it is really inheriting this default from the HTTP spec. > >> If the latter, it would be a reasonable >> candidate for a Connector parameter, perhaps. > > The <Connector> currently has both useBodyEncodingForURI and URIEncoding > attributes for interpreting the URI, but nothing for the encoding of the > body. Since this can easily be done using filters (whereas there is no > way to fiddle with the URI encoding), I doubt it will be added to the > <Connector>. > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAkm/phgACgkQ9CaO5/Lv0PDITQCdGmVpl/GdHee3zAwGkbcUTQiq > pL8AoJWxoH/iAjDlD5SQlirwn0XG5ZwZ > =mwQW > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
