Stefanos Karasavvidis wrote:
If not already done, port the useBodyEncodingForURI parameter to the
next 4.1.x release.
This new flag has been ported last month.
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comm
From a developers point of view however, applying the above two points
a) brakes expected behaviour (setCharacterEncoding() method does not
work the same as before)
b) does not give an acceptable alternative (if all parameter passing
could be solved with POST method, then the GET method would no
Remy Maucherat wrote:
Jess Holle wrote:
Remy Maucherat wrote:
This is a good question -- but one which only applies to POST. My bug
case was explictly with GET.
If there is an entity body encoding specified in the request, then I
am not sure which should override. If there is not, then I wou
Jess Holle wrote:
Remy Maucherat wrote:
This is a good question -- but one which only applies to POST. My bug
case was explictly with GET.
If there is an entity body encoding specified in the request, then I am
not sure which should override. If there is not, then I would presume
setCharacte
Remy Maucherat wrote:
Jess Holle wrote:
Remy Maucherat wrote:
For example:
remm2003/12/10 14:26:28
Modified:catalina/src/share/org/apache/coyote/tomcat5
CoyoteConnector.java CoyoteRequest.java
mbeans-descriptors.xml
Log:
- Add a f
Jess Holle wrote:
Remy Maucherat wrote:
For example:
remm2003/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 en
Remy Maucherat wrote:
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
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'
Remy Maucherat wrote:
Jess Holle wrote:
Remmy, et al:
The API is *not* optional. It is a required part of the servlet spec.
Great. I didn't know that ;-)
How about:
- Not CCing me. I'm subscribed to tomcat-dev already. thanks.
Sorry.
- There's big threads, commit messages (incl recent ones),
Jess Holle wrote:
Remmy, et al:
The API is *not* optional. It is a required part of the servlet spec.
Great. I didn't know that ;-)
How about:
- Not CCing me. I'm subscribed to tomcat-dev already. thanks.
- There's big threads, commit messages (incl recent ones), and bugs on
this issue. How ab
Remmy, et al:
The API is *not* optional. It is a required part of the servlet spec.
It works just great in Tomcat 4.1 and is not an acceptable regression in
Tomcat 5. I am thus one step away from re-opening this bug
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23929)
I cannot use the e
11 matches
Mail list logo
