tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 51881] Server incorrectly parses incoming HTTP requests and loses them
Date Wed, 28 Sep 2011 06:25:23 GMT

--- Comment #8 from Edward Alexandrov <> 2011-09-28 06:25:23 UTC ---
Created attachment 27620
war file

Please also note the message flow. Normally, when opening the page, you should
see 3 messages under 'Received messages' 
1. State: messageReceived, Transport: polling, Body: { "success": true}
2. Pushing body: { "command": "player/reauth", "params": { "token": "ABC" } }
3. State: messageReceived, Transport: polling, Body: { "command":
"system/hello" ...

And when you open the second tab, when the issue arisies you will see only two
of them
1. Pushing body: { "command": "player/reauth", "params": { "token": "ABC" } }
2. State: messageReceived, Transport: polling, Body: { "command":

This is because incoming POST (for Pushing body: { "command": "player/reauth")
is "swallowed" by Tomcat and presented to TransportHandler as GET with
duplicate headers. And if you wait about 20-30sec, you will see the third line
to appear, maybe because of the request is handled for the second time or
something after the timeout.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message