Repository navigation
Fetch passports with httpx over HTTP/2, keep the public-address pinning - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DPP services may refuse HTTP/1.x (DPP-DEX-006). HttpResolver now uses httpx, which negotiates HTTP/2 via ALPN and falls back to HTTP/1.1. The connection stays pinned to the checked public address (httpx option addresses; SNI, certificate check and Host keep the host name), also after redirects. Redirects (max 5), HEAD and ranged GET, per-run cache, header lists and DPPLINT_ALLOW_PRIVATE_NETWORKS are unchanged. retrieval.httpVersion reports the HTTP version of the final response. Tests with a local server cover pinning, refused internal host names, refused redirects to them, header lists, probing and the redirect limit.