feat: redirect to dweb link when ipns #25
Merged
Conversation
This file contains 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
Deploying with
|
| Latest commit: |
4aa8578
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a28b465e.nftstorage-link.pages.dev |
vasco-santos
force-pushed
the
fix/redirect-to-dweb-link-when-ipns
branch
from
55ec21c
to
d423086
Compare
vasco-santos
force-pushed
the
fix/redirect-to-dweb-link-when-ipns
branch
from
d423086
to
4aa8578
Compare
vasco-santos
changed the title
This was referenced Apr 13, 2022
Closed
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 addresses first step to support IPNS. It handles
/ipnsresolution and subdomain resolution by simply redirecting todweb.linkin the end.Redirect to DNS safe representation rules:
-swapped into--and.swapped into-to have valid SSL certificate with sub-sub domainA follow up PR should address adding support for IPNS resolution proxying it to the gateway race. We need to refactor some CID specific logic and (perhaps?) get independent metrics to IPNS response times. (will create an issue)
CF configuration needed changes:
Closes #24