-
-
Notifications
You must be signed in to change notification settings - Fork 806
Up wsproto to 1.0.0 #892
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
Up wsproto to 1.0.0 #892
Conversation
Stop send me please. |
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.
@euri10 LGTM. Let's mark this for 0.14. :)
What does the milestone mark does ? Should I wait to merge until we're
ready to push this new minor ?
…On Wed, Dec 30, 2020, 11:02 PM Florimond Manca ***@***.***> wrote:
***@***.**** approved this pull request.
@euri10 <https://github.com/euri10> LGTM. Let's mark this for 0.14. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#892 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAINSPWB3UFWTGWNMXH34J3SXOPNVANCNFSM4UZPXNWQ>
.
|
care to explain this @florimondmanca ? should I merge or not ? |
@euri10 At the time I thought that if we merged this then it would require the next release to be 0.14 (minor bump rather than patch since this might break things and it's somewhat of an addition). I still think that's the case, but it didn't really mandate blocking anything. Feel free to merge. :) |
Fixes #868
We have a few tests failing if using wsproto 1.0.* vs the one pinned that was 0.15.*
As noticed in the issue, the main difference comes from this diff in
src/wsproto/handshake.py
wherestatus_code=426,
becomesstatus_code=426 if version else 400,
so the 426 we test in
test_supported_upgrade_request
can only appear if there is at least theSec-WebSocket-Version
header, and in order for the 426 to appear it need to bea wrong version.Same reasoning on
test_invalid_upgrade
we provide a wrong sec-websocket-version (11 instead of 13) to trigger the 426 in wsproto and 400 on websockets