Improve performance of starting web requests when content length is not set #9172
Conversation
Reorder the start logic to avoid the check to remove content length if its not present related issue #2779
bdraco
added
backport-3.10
psf-chronographer
bot
added
the
bot:chronographer:provided
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 #9172 +/- ##
=======================================
Coverage 98.31% 98.31%
=======================================
Files 107 107
Lines 34485 34496 +11
Branches 4095 4095
=======================================
+ Hits 33903 33916 +13
+ Misses 411 410 -1
+ Partials 171 170 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Looks like we are missing coverage for this case but it was not obvious before |
bdraco
changed the title
Backport to 3.10: 💚 backport PR created✅ Backport PR branch: Backported as #9192 🤖 @patchback |
(cherry picked from commit b93ef57)
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #9193 🤖 @patchback |
(cherry picked from commit b93ef57)
…b requests when content length is not set (#9192) Co-authored-by: J. Nick Koston <[email protected]>
…b requests when content length is not set (#9193) Co-authored-by: J. Nick Koston <[email protected]>
What do these changes do?
Reorder the start logic to avoid the check to remove content length if its not present
Are there changes in behavior for the user?
no
Is it a substantial burden for the maintainers to support this?
no
related issue #2779
before
after
