https://issues.apache.org/bugzilla/show_bug.cgi?id=49779
--- Comment #3 from Ed Saltelli 2011-07-20 21:25:01
UTC ---
One side-effect of consuming the Request's body is that consumers of the
restored request are forced into using request.getInputStream() i.e. you cannot
attempt to obtain a reader
https://issues.apache.org/bugzilla/show_bug.cgi?id=49779
--- Comment #4 from Konstantin Kolinko 2011-10-20
12:13:52 UTC ---
(In reply to comment #3)
> One side-effect of consuming the Request's body is that consumers of the
> restored request are forced into using request.getInputStream() i.e. y
https://issues.apache.org/bugzilla/show_bug.cgi?id=49779
--- Comment #1 from hanswae...@gmail.com 2010-08-19 05:53:00 EDT ---
also tested against Tomcat v6.0.29 with the same result and against Tomcat v5.5
(I think) which returns the correct return code HTTP 200, but threw internal
exceptions.
--
https://issues.apache.org/bugzilla/show_bug.cgi?id=49779
hanswae...@gmail.com changed:
What|Removed |Added
CC||hanswae...@gmail.com
--
Con
https://issues.apache.org/bugzilla/show_bug.cgi?id=49779
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
