https://bz.apache.org/bugzilla/show_bug.cgi?id=64938
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=64938
--- Comment #6 from Mark Thomas ---
I've implemented the changes agreed in the Jakarta Servlet project for 10.0.x.
They will be in 10.0.3 onwards.
I have started a discussion on the dev@ list to determine if the changes should
be back-ported a
https://bz.apache.org/bugzilla/show_bug.cgi?id=64938
Mark Thomas changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #5 from Mark Thomas ---
https://bz.apache.org/bugzilla/show_bug.cgi?id=64938
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #4 from Mark Thomas
https://bz.apache.org/bugzilla/show_bug.cgi?id=64938
--- Comment #3 from Remy Maucherat ---
According to the javadoc, null is probably not a valid value (it says:
"charset: a String specifying only the character set defined by IANA", so
"null" is obviously not one of these). Unlike other places,
https://bz.apache.org/bugzilla/show_bug.cgi?id=64938
--- Comment #2 from Mark Thomas ---
The behaviour of other Servlet containers is irrelevant. What matters is the
Sevlet specification.
You could argue that the ServletResponse.setCharacterEncoding Javadoc does not
permit null to be passed as t
https://bz.apache.org/bugzilla/show_bug.cgi?id=64938
--- Comment #1 from quaff ---
Jetty is respect this
https://github.com/eclipse/jetty.project/blob/jetty-10.0.x/jetty-server/src/main/java/org/eclipse/jetty/server/Response.java#L1000
--
You are receiving this mail because:
You are the assign
