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
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
Jess Holle wrote:
Remy Maucherat wrote:
-1.
The attribute, now that it actually exists, is well documented.
Yes, but the default behavior should be for setCharacterEncoding() to
work according to general JSP/servlet usage recommendation e.g.:
http://java.sun.com/developer/technicalArticles/I
Remy Maucherat wrote:
-1.
The attribute, now that it actually exists, is well documented.
Yes, but the default behavior should be for setCharacterEncoding() to
work according to general JSP/servlet usage recommendation e.g.:
http://java.sun.com/developer/technicalArticles/Intl/MultilingualJSP/.
Remy Maucherat wrote:
Using different encoding for GET and POST parameters by default
is counter-intuitive and breaks the Principle of least astonishment.
If it is kept that way, the same bug will be reported again and again.
-1.
The attribute, now that it actually exists, is well documented.
R
Martin Kuba wrote:
Hi,
I have found recently that current TomCat 5 uses different
encoding for POST and GET parameters. I was quite surprised,
because all bugs opened for this issue are just closed as invalid
without an explanation.
But after a long searching I found the discussion about bug 23929
Hi,
I have found recently that current TomCat 5 uses different
encoding for POST and GET parameters. I was quite surprised,
because all bugs opened for this issue are just closed as invalid
without an explanation.
But after a long searching I found the discussion about bug 23929 at
http://www.mai
