search

ipfs-inactive / website

This repo has been replaced by https://github.com/ipfs/ipfs-website/
https://github.com/ipfs/ipfs-website/
MIT License
183 stars 128 forks source link

Broken links (IPFS variant only) #223

Closed da2x closed 5 years ago

da2x commented 7 years ago

  1. Visit http://127.0.0.1:8080/ipns/ipfs.io/docs/examples/

  2. Click on “IPFS for websites” in the list of examples

    ipfs resolve -r /ipns/ipfs.io/ipfs/QmNZiPk974vDsPmQii3YbrMKfi12KTSNM7XMiYyiea4VYZ/example: no link named "ipfs" under QmPCawMTd7csXKf7QVr2B1QRDZxdPeWxtE4EpkDRYtJWty

  3. Go back and click on “Blog” (in the top bar)

    ipfs resolve -r /ipns/ipfs.io/blog: no link named "blog" under QmPCawMTd7csXKf7QVr2B1QRDZxdPeWxtE4EpkDRYtJWty

lidel commented 6 years ago

There two bugs at play here.

2) does not happen anymore, but looks like a clash between gateway and dnslink redirect. I fixed similar edge cases in https://github.com/ipfs-shipyard/ipfs-companion/pull/518, fix will land in next release.

3) the problem is that blog is is a separate static website and current URL structure does not translate to dnslinks used.

If user is visiting https://ipfs.io/blog/ and has dnslink lookup enabled in companion extension they get redirected to http://127.0.0.1:8080/ipns/ipfs.io/blog/ which at the moment is a directory with this gem: http://127.0.0.1:8080/ipns/ipfs.io/blog/index.json

A fix is to either: