Skip to content

[websocket] Support redirect #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jfarcand opened this issue May 9, 2012 · 1 comment
Closed

[websocket] Support redirect #102

jfarcand opened this issue May 9, 2012 · 1 comment

Comments

@jfarcand
Copy link
Contributor

jfarcand commented May 9, 2012

If the hanshake fail with a response like

T 127.0.0.1:8000 -> 127.0.0.1:49959 [AP]
HTTP/1.1 302 Found.
Date: Wed, 09 May 2012 18:24:59 GMT.
Location: http://localhost:8000/api/.
Content-Length: 0.

We need to redirect like HTTP is doing.

rlubke added a commit that referenced this issue May 10, 2012
rlubke added a commit that referenced this issue May 10, 2012
@rlubke
Copy link
Contributor

rlubke commented May 10, 2012

Tests added. Issue should be resolved.

@rlubke rlubke closed this as completed May 10, 2012
rlubke added a commit that referenced this issue May 10, 2012
rlubke added a commit that referenced this issue May 10, 2012
jfarcand added a commit that referenced this issue May 14, 2012
rlubke added a commit that referenced this issue Jun 21, 2012
* ahc-1.7.x:
  Fix javadoc warnings.
  Integrate Grizzly 2.2.10.
  Fix for the Grizzly side of #101 : [websocket] onError must not be called when status code is != 101.
  Fix for #111 - [websocket] Both Netty and Grizzly issues with URI without port.
  Incremental fix for #101 [websocket] onError must not be called when status code is != 101. Fix Netty side
  Fix for #111 https://github.com/sonatype/async-http-client/issues/111
  Fix errror with clirr
  Port #102 tests
  Port fix for #102 [websocket] Support redirect
  Bump to the latest Netty release
cs-workco pushed a commit to cs-workco/async-http-client that referenced this issue Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants