-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Return rejection if WebSocket
request couldn't be upgraded
#1135
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest somebody who actually knows stuff about WebSockets should review this.
@jplatte I've changed the rejection to specifically call out not being able to upgrade the connection, perhaps because its http/1.0 |
@jplatte gentle ping (: |
I still don't think I'm the right person to review this though 😅 |
In that case I think I'll just yolo it. Its a pretty safe change and given what sean said it should be correct. |
* Return rejection if `WebSocket` request couldn't be upgraded * make rejection about connection upgrades * changelog links
Fixes #1132
Rather than panicking we'll return a rejection. Unfortunately hyper doesn't give any details about why the connection couldn't be upgraded.