You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
Above URL fails at DNS lookup stage because
broken-example.com
domain name does not exist. This producesNS_ERROR_UNKNOWN_HOST
on Firefox andnet::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 todweb.link
should be enough.cc @colinfruit
The text was updated successfully, but these errors were encountered: