It's currently not as convenient to write servlets which support forms input
encodings other than the minimalist US-ASCII ...  rather than only having a
single argument form parseQueryString(String theString), there should be
another version that specifies the encoding:

    Hashtable HttpUtils.parseQueryString(String theString, String encoding);

Similarly with the parsePostData method.

Note that this supports the convention that's been pushed by Netscape:

 http://people. customer .com/ftang/paper/unicode11paper/t005.html

as well as the more recent (March 1998) approach presented at the IETF:

 ftp://ietf.org/internet-drafts/draft-masinter-url-i18n-01.txt

Both require encoding into bytes, then URL-encoding.

[ above by original submitter ]

N/A

localization is being addressed with the servlet 2.2 specification
although i'm not sure it will directly address HttpUtils.parseQueryString()

I think needs encoding support when make Servlet engine or Pure Java Web
Server.

Now have to wait? Why always waiting!

it's been almost two years
and Java technology is generally so good at i18n support