Accept HTTP 307 Temporary Redirect status along with 302 about websocket-client

[xmuskrat]

So, this means that you choose to support 301 and 302 redirects, but not 307 redirects because clients can, but are not required, to follow 3xx standards? Sad, cause I'm hitting this same issue.

[engn33r]

The link you provided is to the HTTP Semantics RFC, but the relevant text in the WebSockets hybi-13 spec that this repository supports is:

If the status code received from the server is not 101, the client handles the response per HTTP [RFC2616] procedures, in particular the client might perform authentication if it receives 401 status code, the server might redirect the client using a 3xx status code (but clients are not required to follow them), etc. Otherwise, proceed as follows.

[engn33r]

The fix was provided in commit 69468ad but a new version has not been made yet. Please use the latest commit for this feature for now.

The text I provided before was clarification because the OP mentioned a RFC that was not the websocket RFC

[jakublATopera]

I've had a feeling that since WebSocket RFC release, ws release didn't change, but HTTP protocol WS RFC refers to was changed with addition of mentioned status codes (307, 308), so I just pointed the HTTP change.
Thanks for fix.

[engn33r]

@jakublATopera I forgot to push a new release last week, this is now fixed in 1.6.4