[jboss-jira] [JBoss JIRA] (JBWEB-238) HTTP Upgrade API Broken

Fri Apr 13 16:56:47 EDT 2012

    [ https://issues.jboss.org/browse/JBWEB-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12684085#comment-12684085 ] 

David Lloyd commented on JBWEB-238:
-----------------------------------

I think the interesting question will be, "in the same read as what?" - Surely Safari can't expect all HTTP reply headers to appear in a single read.  If you go over the MTU you're guaranteed to have more than one read no matter what.  So is it the same read as the final CRLF after the headers, or something else perhaps?

> 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