It turns out the problem was with the AsyncContext timing out and then writing
to the HttpServletResponse afterward.
Be sure to use an AsyncListener to be notified of these events.
Hopefully this might help someone with a similar problem in the future.
- Chris
On April 13, 2011 11:12:30 am
I'm seeing an intermittent problem with my webapp where a request is sent and
the response contains 8184 bytes from some other response followed by the
correct response.
The setup being used is Nginx 0.8.54 reverse proxying to Tomcat 7.0.11. AJP is
the protocol between Nginx and Tomcat.
The
Hi.
An earlier message to this list [[SECURITY] CVE-2011-1475 Apache Tomcat information
disclosure] /may/ have something to do with this.
(It talks only about the HTTP connector, but also about content mixup with async requests,
so maybe there is a link)
Chris Dumoulin wrote:
I'm seeing an
Actually, I saw that notice and tried Tomcat 7.0.12, but saw the same
behaviour. I should have mentioned that before.
So, I think this is a different issue.
- Chris
On April 13, 2011 07:27:51 am André Warnier wrote:
Hi.
An earlier message to this list [[SECURITY] CVE-2011-1475 Apache Tomcat
In a discussion on Bug 50957
(https://issues.apache.org/bugzilla/show_bug.cgi?id=50957) Mark Thomas said the
following:
Experience has shown that most instances of this type of error are triggered by
application bugs rather than Tomcat bugs - usually in the form of retaining and
re-using a
