Repository navigation
Add 301/302 URL redirect controls to network records - #268
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.
Names on /net/records now have a URL redirect form: enter a complete HTTPS destination, choose 301 permanent or 302 temporary, and save or remove with inline feedback. Existing registration destinations appear as 302 redirects. The gateway returns the selected status and exact destination, including its path and query.
Owner-only APIs validate active local ownership, reject self redirects and conflicting AAAA/CNAME records, and publish destination/status changes through federation. The additive schema keeps legacy destinations intact. Public DNS and HTTPS provisioning remain prerequisites for reaching the gateway.
Validation: 158 tests passed (4 environment-dependent skips); syntax and signed-reference checks passed. Browser checks at 1440px and 390px cover create 301, reload persistence, change 302, validation/input retention, remove, no forced refresh, and no horizontal overflow. Integration checks verify actual gateway Location/status responses, authorization, namespace suspension and DNS conflicts.