-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Pass response to WSServerHandshakeError #701
Comments
I believe you actually need status code and headers only, not the whole response. |
Fixed by #706 |
@asvetlov can we re-open this issue ? since ws_connect actually makes troubleshooting connection errors very difficult as the response in our case contains detailed error information. |
Please create a new one with detailed description of your problem. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs. |
It might be useful to be able to reference the response when capturing a
WSServerHandshakeError
. The response object also doesn't seem to get closed when the client consumes this error.The text was updated successfully, but these errors were encountered: