-
Notifications
You must be signed in to change notification settings - Fork 227
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
Get stream on handshake error #51
Comments
I think it's possible, but it would require some changes in NB: If you just need to drop the stream, it will be dropped anyways, as |
Hi! What is the state of this Issue? Is there any idea in mind to return a I'm in a situation where I need to deregister the stream from the poll registry if the handshake fails. Since the Thanks! |
I have not yet got acknowledgement from the reporter if the behavior that I described in the previous comment is the one that he would expected. There has been no progress on this issue so far.
So you're using it in conjunction with |
Thanks for the notification. Yeah, I'm using it with Until I know from the
EDIT: I took a deeper look and I can confirm that a |
Based on your comments, the only [temporary] dirty hack that comes to my mind is to wrap the |
If the input stream is not tcpstream but other layers based on it. We may hard to use Drop. Can you provide another callback for such error? So developer can use this callback to customize error response. |
I'm using mio and tungstenite, and it would be nice to have a way to discard the handle when being refused a handshake:
The text was updated successfully, but these errors were encountered: