Martin Kuba wrote:
Stefanos Karasavvidis wrote:

This is getting ridiculous.
Both sides have strong arguments.
I hadn't thought about this issue until tomcat changed it's behaviour, and maybe the Sun folks didn't do it as well.


This should really be clarified within the specification (and I hope they come up with a solution that allows us to continue using GET parameters as we were used to as this is an absolute necessity... maybe by introducing a new method or a second parameter).

Although I do not expect too much, I 've just sent a comment to JSR53 and JSR154

Sorry, nobody answered my previous question. What is the strong argument for breaking backward compatibility ?

The RFC 2396 (URI syntax) in part "2.1 URI and non-ASCII characters"
states that:

   However, there is currently
   no provision within the generic URI syntax to accomplish this
   identification. An individual URI scheme may require a single
   charset, define a default charset, or provide a way to indicate the
   charset used.

   It is expected that a systematic treatment of character encoding
   within URI will be developed as a future modification of this
   specification.

It means that URL character encoding is not defined by standards.
So the only problem which I see is that Tomcat suddenly breaks
the de facto standard used for last ten years and tries to
stop application to use GET parameters.

The decision has been made and was argumented. Please look into the archives of the mailing list. Please stop whining, this will not be changed. Since I wasted too much time already on this, I will ignore all subsequent threads/reply/etc on this particular subject, and will vote -1 to any proposal to change this.


If you cannot be bothered into adding a parameter in the configuration file to enable the behavior you want, I suggest you try to look for another server.

The change to the 4.1.x branch was not intended, and is a bug.
The change to the 5.0.x branch was on purpose (and is a new branch, so expect at least *some* changes in behavior).


Rémy



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to