feat: recover from DNS failures, support DNSLink for .eth #797
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
lidel
force-pushed
the
feat/support-ens-eth-tld
branch
3 times, most recently
from
4365439
to
b6d744d
Compare
This adds support for recovery from DNS lookup failures, and recovery for all HTTP Codes >= 400 When a third-party IPFS gateway is discontinued or censored at DNS level, IPFS Companion will retry request using currently active gateway set by user (public or local). This includes websites backed by DNSLink.
lidel
force-pushed
the
feat/support-ens-eth-tld
branch
from
b6d744d
to
f47e50f
Compare
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 builds on top of #783 and:
.ethDNS failures bu reopening website on EthDNS gateway at.eth.linkMotivation
When a third-party IPFS gateway is discontinued or censored at DNS level, the IPFS Companion should retry request using currently active gateway set by the user (public or local).
We also want to recover in situation when website with DNSLink has a valid DNS
TXTrecord, but HTTP behindArecord is down or unreachable.Note: right now the only real use for DNS recovery is support .eth TLD via .eth.link gateway, however in the future this could provide means of working around DNS-based censorship (eg. by executing DNSLink lookups over libp2p as a fallback).
closes #678, closes #640, #783 needs to be merged first
TODO
.ethcan be supported natively by go-ipfs, or do we need to point at.eth.linkfor now.eth, using.eth.linkfor now.ethtests