Skip to content
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

[websocket] onError must not be called when status code is != 101 #110

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

[websocket] onError must not be called when status code is != 101 #110

jfarcand opened this issue May 15, 2012 · 1 comment
Assignees
Milestone

Comments

@jfarcand
Copy link
Contributor

Instead the onClose(code,status) must be called with code ==102 like Browser are doing.

@slandelle
Copy link
Contributor

@jfarcand Hey boss! What's the status of this?

jfarcand added a commit that referenced this issue Jan 23, 2014
@ghost ghost assigned jfarcand Jan 23, 2014
jfarcand added a commit that referenced this issue Jan 24, 2014
jfarcand added a commit that referenced this issue Jan 24, 2014
jfarcand added a commit that referenced this issue Jan 30, 2014
jfarcand added a commit that referenced this issue Jan 30, 2014
cs-workco pushed a commit to cs-workco/async-http-client that referenced this issue Apr 13, 2023
cancel should be done with outbound user event
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