Bug 58623 - WebSocket client should handle 302 redirect
Summary: WebSocket client should handle 302 redirect
Status: RESOLVED DUPLICATE of bug 57767
Alias: None
Product: Tomcat 7
Classification: Unclassified
Component: WebSocket (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-18 12:02 UTC by Mark Thomas
Modified: 2015-11-22 16:53 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Thomas 2015-11-18 12:02:58 UTC 
Currently, the WebSocket client fails to connect if it receives a 302 redirect.

It would be a useful enhancement to follow the redirect.
Comment 1 Remy Maucherat 2015-11-18 12:27:26 UTC 
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 ...
Comment 2 Mark Thomas 2015-11-22 16:53:28 UTC 

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