-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Fix issue 6652: Raise aiohttp.ServerFingerprintMismatch
exception o…
#6653
Conversation
…n client-side if request through http proxy with mismatching server fingerprint digest
Can we add a test to cover this case? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6653 +/- ##
=======================================
Coverage 98.56% 98.56%
=======================================
Files 107 107
Lines 34949 34981 +32
Branches 4139 4150 +11
=======================================
+ Hits 34446 34478 +32
Misses 335 335
Partials 168 168
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
OK, will have a try. |
I had added a test: "test_https_connect_fingerprint_mismatch", please help to have a review, thanks! |
Hi, There remains one item: "Documentation reflects the changes" in the checklist not done yet. But I checked related document, seems there is no need to add document for this bug fix, any ideas? Thanks! |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Backport to 3.11: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply e3b1011 on top of patchback/backports/3.11/e3b1011f2146ad0faa4c3d3c29f26b73e1400564/pr-6653 Backporting merged PR #6653 into master
🤖 @patchback |
Fix issue 6652: Raise
aiohttp.ServerFingerprintMismatch
exception on client-side if request through http proxy with mismatching server fingerprint digestWhat do these changes do?
Fix issue 6652: Raise
aiohttp.ServerFingerprintMismatch
exception on client-side if request through http proxy with mismatching server fingerprint digestAre there changes in behavior for the user?
Users will be able to verify server certificate fingerprint for requests which go through http proxy
Related issue number
Fixes #6652
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.