I sorted it out moments later of posting this mail.
It was a mistake from my side.
Thanks any sorry for any inconvenience, if caused.
But there is still something I am curious about. How does Tomcat 4.1.x
deal with HTTP requests that have *transfer-coding=chunked*?
Santosh.
Santosh Puranshettiwar wrote:
1. a POST request
2. all request parameter (in form of key-value pairs) in the message body
3. application/x-www-form-urlencoded
4. (need more? ... please tell me.)
Normally, the parameterMap (for HttpServletRequest.getParameter()
method) is not built. But when I use a RequestDumperValve in between,
everything works fine.
Why would this happen?
Santosh.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
