Decoding of query characters ignores setCharacterEncoding

Deduced from static code inspection of 6.1.0rc3. in org.mortbay.jetty.Request#extractParameters()

There are two values defining the character encoding:
the instance member '_queryEncoding' and local variable 'encoding'.

In a deployed Jetty installation where the user is only ever using runtime parameters
and/or the published Servlet APIs, '_queryEncoding' can only ever be given a value
by using the 'org.mortbay.jetty.Request.queryEncoding' parameter.

It thus acts as a server-wide default value, individual servlets cannot set its value.

What they are supposed to do is call the servlet API HTTPServlet#setCharacterEncoding(String).
The parameter of this call is used in Request.extractParameters() by
String encoding = getCharacterEncoding(); // Request line 1222

The key method invocation, where I believe the bug is, is in line 1227:

_uri.decodeQueryTo(_baseParameters,_queryEncoding);

Note that this uses '_queryEncoding', not 'encoding'.

So the only current way of specifying the encoding used to decode the query is via
the server-wide 'org.mortbay.jetty.Request.queryEncoding' parameter.

I think the logical solution would be to prefer any specific encoding set via the Servlet
'setCharacterEncoding()' API , defaulting to the _queryEncoding.

So I would propose changing line 1227 to

_uri.decodeQueryTo(_baseParameters, (encoding!=null?encoding:_queryEncoding) );