|Summary:||WebSocket client should handle 302 redirect|
|Product:||Tomcat 7||Reporter:||Mark Thomas <markt>|
|Component:||WebSocket||Assignee:||Tomcat Developers Mailing List <dev>|
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 ...