-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bill,
Bill Barker wrote:
| The HTTP spec specifies that header information is encoded in iso-latin-1
Could you provide a reference for this? Whenever I dig into the HTTP
specification, I end up having to read all over it to find things like
this. I seem to recall that:
1. I've located this information in the past
2. The real answer was that HTTP headers format inherits from SMTP
3. SMTP requires pure ASCII headers
4. The request line ("GET /whatever HTTP/[version]") does not count
~ as a header
Unfortunately, I can't find my references and so my assertions are
pretty much worthless. :(
| so this is what Tomcat uses by default when parsing the query-string. If
| you want the non-default behavior, then simply set
| useBodyEncodingForURI="true" in the <Connector ... /> element of
server.xml.
I find it more useful to set URIEncoding="UTF-8" in the <Connector>,
since the page encoding and URI encoding are not guaranteed to be the
same. The OP should look to see what works best and feels more natural
in his environment.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkiRydQACgkQ9CaO5/Lv0PBDmwCdFOiGgB33MNXvkyk2rJD4/Qru
CvwAn1h8Ex8bpoMo9CyOYKG1JqjzCE1y
=UeRV
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: [email protected]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
