Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recover from dead Subdomain Gateways #800

Closed
lidel opened this issue Oct 17, 2019 · 0 comments · Fixed by #802
Closed

Recover from dead Subdomain Gateways #800

lidel opened this issue Oct 17, 2019 · 0 comments · Fixed by #802

Comments

@lidel
Copy link
Member

lidel commented Oct 17, 2019

Continuation of #640, and #797, cc https://github.com/ipfs/ipfs/issues/337, ipfs/in-web-browsers#89

Motivation

We now have a framework for recovering from failed HTTP responses to Path Gateways and DNSLink websites. To make it feature-complete we should do the same for Subdomain Gateways.

Details

https://bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq.ipfs.broken-example.com/wiki/

Above URL fails at DNS lookup stage because broken-example.com domain name does not exist. This produces NS_ERROR_UNKNOWN_HOST on Firefox and net::ERR_NAME_NOT_RESOLVED on Chromium, which are already supported since #797.

We want to recover from this by redirecting failed subdomain-based gateways to dweb.link (our canonical subdomain gateway):
https://{cid}.ipfs.dweb.link/path/

In the future, when we have support for {cid}.ipfs.localhost (ipfs/in-web-browsers#109), we will also redirect to local node, but for now redirect to dweb.link should be enough.

cc @colinfruit

@lidel lidel added the help wanted Seeking public contribution on this issue label Oct 17, 2019
@lidel lidel removed the help wanted Seeking public contribution on this issue label Oct 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant