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

[Mike Brock (JIRA)]

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

Mike Brock edited comment on JBWEB-238 at 4/13/12 12:37 PM:
------------------------------------------------------------

Yes. I'm sure clients can understand it. I have a patched version of AS with which I've been testing iPhones, iPads, Android Tablets, Safari, etc.  all week. 

I don't think these changes increase the complexity at all from the Servlet point of view. That's why my patch adds an overloaded sendUpgrade method.

Also, most people will use higher level frameworks like Errai or Stilts or Atmosphere. So most users won't care about this. :)
                
      was (Author: cbrock):
    Yes. I'm sure clients can understand it. I have a patched version of AS with which I've been testing iPhones, iPads, Android Tablets, Safari, etc.  all week. 

I don't think these changes increase the complexity at all from the Servlet point of view. That's why my patch adds an overloaded sendUpgrade method.

Also, most people will use higher level frameworks like Errai or Stilts or Atmosphere. So most users won't care about this. :(
                  
> 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: JBossWeb.patch
>
>
> 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