https://issues.apache.org/bugzilla/show_bug.cgi?id=50065
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #3 from Mark Thomas <ma...@apache.org> 2010-10-10 05:50:55 EDT ---
(In reply to comment #2)
> Javadoc for java.net.URLEncoder makes reference to
> http://www.w3.org/TR/html40/appendix/notes.html#non-ascii-chars and says that
> its preferable to utf-8 instead of iso-8859-1. I believe that utf-8 is a more
> reasonable default choice than iso-8859-1 is.
That is a suggestion, not a mandatory requirement. Tomcat provides an option
for you to change the default to UTF-8 if you wish.
> Secondly, javadoc for HttpServletRequest::setRequestEncoding() seems
> ambiguous to me. It indeed mentions only the request body, but it also says
> "prior to reading request parameters or reading input". This "prior to reading
> request parameters" can, of course, be an implementation detail, but to me it
> seems reasonable to think that parameter decoding is influenced by choice of
> the request encoding.
Request parameters can appear in the request body.
All the options necessary to implement the behaviour you are looking for are
already available. There is certainly no bug (as in a breach of the spec
requirements) here.
There is an argument for changing the default encoding but that would be an
enhancement request which, if memory serves correctly, already exists. Feel
free to add comments there.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
