-
-
Notifications
You must be signed in to change notification settings - Fork 2.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
Ensure Cython WebSocket parser can handle frames of 2**23 in size #9781
Conversation
This is technically allowed if the limit is increased high enough https://www.rfc-editor.org/rfc/rfc6455#section-5.2 However its unlikely to happen since you would need 9.22 exabytes of RAM assuming there is no copy of the message ever
CodSpeed Performance ReportMerging #9781 will not alter performanceComparing Summary
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #9781 +/- ##
=======================================
Coverage 98.68% 98.68%
=======================================
Files 117 117
Lines 35968 35968
Branches 4276 4276
=======================================
Hits 35494 35494
Misses 319 319
Partials 155 155
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #9782 🤖 @patchback |
) (cherry picked from commit 8116257)
… handle frames of 2**23 in size (#9782) Co-authored-by: J. Nick Koston <nick@koston.org>
What do these changes do?
This is technically allowed if the limit is increased high enough https://www.rfc-editor.org/rfc/rfc6455#section-5.2
However its unlikely to happen since you would need at least 9.22 exabytes of RAM assuming there is no copy of the message ever
The default max message size is 4194304 so this went unnoticed
Are there changes in behavior for the user?
no
Is it a substantial burden for the maintainers to support this?
no