Discovery: follow same-eTLD+1 redirects when fetching metadata#18
Open
rohanharikr wants to merge 1 commit into
Open
Discovery: follow same-eTLD+1 redirects when fetching metadata#18rohanharikr wants to merge 1 commit into
rohanharikr wants to merge 1 commit into
Conversation
Defines redirect-handling behavior for metadata fetches: - MUST follow redirects within the same eTLD+1 - SHOULD NOT follow redirects across eTLD+1 boundaries - Validation (issuer match, iss claim) is performed against the post-redirect URL Allows deployments where the user-facing entry point and the canonical metadata host differ within the same registrable domain (e.g. hello.coop → person.hello.coop). Either URL can serve as a valid discovery entry point. Closes dickhardt#14
rohanharikr
force-pushed
the
discovery-follow-same-etld-redirects
branch
from
9de5a87 to
2d7d5d1
Compare
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.
Closes #14
Adds a
Following Redirectssubsection to## Metadata Documentsdefining HTTP redirect behavior during metadata discovery.What's normative
issclaim) is performed against the final URL, not the originalWhy
Allows deployments where the user-facing entry point and the canonical metadata host differ within the same registrable domain. Concretely:
hello.coophttps://hello.coop/.well-known/aauth-person.jsonhttps://person.hello.coop/.well-known/aauth-person.jsonissuerishttps://person.hello.coop— matches post-redirect URL ✓This works without protocol changes today only if implementations happen to follow redirects, and the issuer match works only if it's done against the post-redirect URL — both currently unspecified. This PR makes the behavior explicit and bounded.
Cross-reference
The post-redirect issuer check ties in with #12 (require
metadata.issuer === fetched-URL). PR #17 mandates the check; this PR clarifies it applies to the post-redirect URL.Diff scope
One new
### Following Redirects {#metadata-redirects}subsection in the Metadata Documents section. Three short paragraphs.