[jboss-jira] [JBoss JIRA] (JBWEB-238) HTTP Upgrade API Broken
[
https://issues.jboss.org/browse/JBWEB-238?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JBWEB-238:
-----------------------------------
It may be a coincidence/red herring. Yes, Remy's solution does send the handshake
bytes in a separate TCP message. However the problem appears to be something else - the
server sends a FIN before it could ever know the client's opinion of the reply. Remy,
do you know of some reason this would happen on an Upgraded socket?
HTTP Upgrade API Broken
-----------------------
Key: JBWEB-238
URL: https://issues.jboss.org/browse/JBWEB-238
Project: JBoss Web
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: JBossWeb-7.0.13.GA
Environment: Any
Reporter: Mike Brock
Assignee: Remy Maucherat
Attachments: cdidemo2.war, JBossWeb.patch, Upgrade00ServletTest.java
The HTTP Upgrade API currently does not permit reading and writing to the
ServetOutputStream and ServletInputStream during the initial negotiation. All of the data
is swallowed until after the negotiation and head exchange.
Unfortunately this is insufficient as some WebSocket Draft Specification rely on data
within the body of the request and response as part of the handshake.
The attached patch fixes this problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira