https://issues.apache.org/bugzilla/show_bug.cgi?id=50504
--- Comment #6 from Mark Thomas ---
The query string remains as bytes until it is required (if at all). Take a look
at Http11InputBuffer.parseRequestLine() in trunk and when it is called.
Hence why setting the character encoding on the req
https://issues.apache.org/bugzilla/show_bug.cgi?id=50504
--- Comment #5 from Christopher Schultz ---
(In reply to Mark Thomas from comment #4)
> Request URI decoding has to bee connector wide since the URI has to be
> decoded before it is mapped.
If it can be assumed that the mapping has been do
https://issues.apache.org/bugzilla/show_bug.cgi?id=50504
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=50504
--- Comment #3 from Attila Király 2011-09-21
05:17:51 UTC ---
A Valve could be a solution too if it comes with Tomcat. It would mean that
encoding can be configured per webapp which is what this ticket is about.
--
Configure bugmail: htt
https://issues.apache.org/bugzilla/show_bug.cgi?id=50504
--- Comment #2 from Christopher Schultz
2011-09-20 21:50:03 UTC ---
Couldn't this just be written as a Valve?
The only utility I can see for checking for a request attribute like
"org.apache.tomcat.request.query_encoding" would be to have
https://issues.apache.org/bugzilla/show_bug.cgi?id=50504
Attila Király changed:
What|Removed |Added
CC||kiralyattila...@gmail.com
--
Conf
https://issues.apache.org/bugzilla/show_bug.cgi?id=50504
--- Comment #1 from Attila Király 2010-12-21
04:17:22 EST ---
Created an attachment (id=26432)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=26432)
Patch implementing the suggestion + junit test
Attaching patch.
--
Configur
