The terms encoded and decoded need further definition. If you are
referring to a GET request and parameters in the URL, the answer is
decoded. All the %27s and the like are decoded to their character
equivalent. URLs themselves are ASCII character sets per RFC 1738 (at
least that's what HTML 4.0.1 cites).
If you are referring to internationalization and character set encoding
in POST requests, SRV.4.9 of the servlet spec (I'm reading servlet spec
2.4 here) describes how the servlet container is to deal with it. If
the browser actually sent character encoding information in the
Content-Type header, that encoding is used and the encoding is provided
by request.getCharacterEncoding(). If no character set encoding is
provided, the default ISO-8859-1 encoding is used and
request.getCharacterEncoding() returns null.
--David
Mark H. Wood wrote:
If there's a better place to ask, please direct me.
I'm tracking down a problem with third-party code which looks more and
more like double URI-decoding. But I can't find anywhere in the
servlet documentation where it says whether getParameter returns
decoded or encoded data.
???
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
