Skip to content

Added StatusCodeError when receiving unexpected status code #234

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

Merged
merged 1 commit into from
Jul 13, 2019

Conversation

jean-airoldie
Copy link
Contributor

Fixes #233.

While this is theoretically a breaking change, I'm unsure if its that significant.

@vi
Copy link
Member

vi commented Jul 13, 2019

I'll include it when I release #222-based version which also breaks error handling in user code.

@vi
Copy link
Member

vi commented Jul 13, 2019

On the second though, #236 is also technically unstabilizing (websocket can start leaking username and password that was previously ignored), so bumping major version and releasing anyway with this as well.

@vi vi merged commit 7f8f877 into websockets-rs:master Jul 13, 2019
@vi
Copy link
Member

vi commented Jul 13, 2019

Published v0.23.0.

@jean-airoldie jean-airoldie deleted the status_code_error branch July 13, 2019 21:15
@jean-airoldie
Copy link
Contributor Author

@vi Nice, thanks!

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

Successfully merging this pull request may close these issues.

Allow retrieval of StatusCode in connection error
2 participants