You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2015/11/18 13:02:58 UTC

[Bug 58623] New: WebSocket client should handle 302 redirect

https://bz.apache.org/bugzilla/show_bug.cgi?id=58623

            Bug ID: 58623
           Summary: WebSocket client should handle 302 redirect
           Product: Tomcat 7
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: WebSocket
          Assignee: dev@tomcat.apache.org
          Reporter: markt@apache.org

Currently, the WebSocket client fails to connect if it receives a 302 redirect.

It would be a useful enhancement to follow the redirect.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

[Bug 58623] WebSocket client should handle 302 redirect

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=58623

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #2 from Mark Thomas <ma...@apache.org> ---


*** This bug has been marked as a duplicate of bug 57767 ***

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

[Bug 58623] WebSocket client should handle 302 redirect

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=58623

--- Comment #1 from Remy Maucherat <re...@apache.org> ---
That's included in 57767 (for trunk).

I looked a bit at Tyrus, and it is a fairly standard HTTP client (with a lot of
proprietary config for all its features), while the websockets client in Tomcat
can't do anything besides upgrade. OTOH, a webapp that needs a websocket client
does not need to use the Tomcat one, so a valid strategy could be to do
nothing. Which is nice since ultimately the only real solution is to use HTTP
client or something big like that ...

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org