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

Mike Brock (JIRA) jira-events at lists.jboss.org
Fri Apr 13 12:53:49 EDT 2012


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

Mike Brock commented on JBWEB-238:
----------------------------------

I thin it is wrong-headed to not support this. You've just basically refused to support every iOS device and many Android devices for no good reason other than you don't think it looks like "broken HTTP". Well, good for you. Some us ACTUALLY are trying to compete in a market where supporting as many clients as possible actually MATTERS.
                
> 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
>
>
> 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

        


More information about the jboss-jira mailing list