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
When accessing via a subdomain gateway it is unable to resolve
ipfs resolve -r /ipfs/bafybeidu5fa3wnoj6ixuluw6h5otbnsicgwbma7xhnao7zs3wpcn3nj7te/ipfs/bafybeiczbt5m3sox6r7drnzhg5dln33vffy372b42x2v7pmchncqrbbxxu: no link named "ipfs" under bafybeidu5fa3wnoj6ixuluw6h5otbnsicgwbma7xhnao7zs3wpcn3nj7te
Could change the hash replace to <cid>.ipfs.localhost:8080/#<decryption_key>-firstview
The text was updated successfully, but these errors were encountered:
Thanks, I haven't actually looked at IPFS in a long time.
From what you've said, in principle I agree. We'd want to detect if it's a subdomain gateway (How? Do we just check if the domain looks like ipfs.$foo? What about ipfs.io or other public non-subdomain gateways? Or are they subdomain gateways now too? Maybe we just check for a cid at the start of the domain?), and if it looks like it's a subdomain gateway, then do what you said.
It's unlikely I'll implement this but I'd merge a sensible pull request.
When accessing via a subdomain gateway it is unable to resolve
Could change the hash replace to
<cid>.ipfs.localhost:8080/#<decryption_key>-firstview
The text was updated successfully, but these errors were encountered: