Repository navigation
Sign the port along with the host - #3965
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
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.
Fixes #
Proposed changes:
host, RFC 9421 as@authority. WordPress sendsHostwith the port whenever it is not the scheme's default (cURL and fsockopen both do), so a server on a non-default port could not verify our signatures. RFC 9421@target-urialready had the port.get_authority( $url )returns the host plus the port when it is not 80/443 for http/https, the way RFC 9110 definesHost. Both signers use it.Other information:
Requests on the default ports are unchanged, the port is only added when the URL has a non-default one. I did not set
Hostexplicitly insign(), because Requests would then send the sameHostalong on redirects to another host.Testing instructions:
vendor/bin/phpunit --filter 'test_get_authority|test_sign_names_a_non_default_port'example.org:8443and verify with thatHost. Without the change both fail.Changelog entry
Changelog Entry Details
Significance
Type
Message