Jess Holle wrote:
- There's big threads, commit messages (incl recent ones), and bugs on this issue. How about reading that before writing an email about how bad things are.
I did search the archives for such threads before even filing my duplicate bug, so apparently my searching is inept. I'll look again, but pointers would be appreciated.
For example: remm 2003/12/10 14:26:28
Modified: catalina/src/share/org/apache/coyote/tomcat5
CoyoteConnector.java CoyoteRequest.java
mbeans-descriptors.xml
Log:
- Add a flag to allow using the encoding specified in the contentType for
the URI paramters. This is disabled by default, not compliant with the standards,
but present for compatibility.
But as per my previous message I /cannot /change this on a connector basis. I /must /make this determination on a per-request basis -- /and the servlet spec specifically allows me to do this via the setCharacterEncoding() API as I read it/.
There's a query page in BZ, also, and as I said, many threads on tomcat-dev (use the archives).
I queried both at some length -- especially BZ. I'll query the tomcat-dev archives further, but again a simple synopsis of how Tomcat's behavior satisfies the spec and is thus not a bug attached to the bug would save everyone a lot of trouble in cases like this. In other words, where a bug that from all indications appears to be a spec violation is closed as "INVALID" an explanation attached to the bug itself would be a *very* good idea.
-- Jess Holle
