subdomain gateway: clarify PSL and eTLD best practices #500
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
🚀 Build Preview on IPFS ready
|
bumblefudge
reviewed
Apr 4, 2025
bumblefudge
reviewed
Apr 4, 2025
bumblefudge
reviewed
Apr 4, 2025
bumblefudge
reviewed
Apr 4, 2025
bumblefudge
approved these changes
Apr 4, 2025
Co-authored-by: Bumblefudge <bumblefudge@learningproof.xyz>
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.
This PR aims to clarify Public Suffix List and eTLD best practices under existing security considerations section in notes for implementers.
It was already there, but easy to miss + did not mention what may happen of PSL entry is not present.
cc @mishmosh @bumblefudge @darobin @2color for visibility / feedback – this was discussed at recent IPFS Protocol WG