IPFS experiments

This repo is a simple wrapper repo and set of test files used for my experiemnts with IPFS.

Reference

• https://talk.fission.codes/t/redirects-manifests-and-content-type-for-ipfs-gateway/2297
• ipfs/specs#257
• ipfs/kubo#7392

Current work

fission-codes/kubo#4

Set up IPFS and test basic redirects

• . envsetup.sh
• git submodule update --init
• ipfs_build_and_run daemon (this builds and runs ipfs)
• open http://localhost:5001/webui in browser
• create a new folder named test
• upload the contents of test-ipfs-files to your test folder in ipfs.
• navigate up and click share link for test folder, you'll get something like: https://ipfs.io/ipfs/SOMECID
• now you can modify link to browse on local http gateway by replacing https://ipfs.io with http://localhost:8080. Ex: http://localhost:8080/ipfs/SOMECID
  • this will serve the contents of the index.html file you uploaded.
• getting a non-existant file should give you the contents of ipfs-404.html
• test _redirects
  • browsing to http://localhost:8080/ipfs/SOMECID/test should redirect you to the / and serve up the index file.
  • browsing to http://localhost:8080/ipfs/SOMECID/hir should redirect you to hi.html and serve up this file.
  • browsing to http://localhost:8080/ipfs/SOMECID/hi should leave the URL the same and serve the hi.html file contents.
  • browsing to http://localhost:8080/ipfs/SOMECID/hi/there should leave the URL the same and serve the hi.html file contents.

Note, every time you update or change a file in the test directory, the CID of the test directory changes!

Notes on go-ipfs http gateway operation

• if path is directory, and index.html exists in that dir, than that file is served without a redirect
• if file is not found in directory, then ipfs-404.html is served with 404 code

Reference of other implementations

go has http.Redirect function.

Cloudflare

Cloudflare supports a _redirects file with format of:

[source] [destination] [code?]

Examples:

/home301 / 301
/home302 / 302
/querystrings /?query=string 301
/twitch https://twitch.tv
/trailing /trailing/ 301
/notrailing/ /nottrailing 301
/blog/* https://blog.my.domain/:splat
/products/:code/:name /products?code=:code&name=:name

Cloudflare plans to use 200 code (similiar to Netlify) for Proxying -- likely similiar to rewrite.

Netlify

• https://docs.netlify.com/routing/redirects/rewrites-proxies/

When you assign an HTTP status code of 200 to a redirect rule, it becomes a rewrite. This means that the URL in the visitor’s address bar remains the same, while Netlify’s servers fetch the new location behind the scenes.

Appears to use the _redirects file as well.

NGINX

https://nginx.org/en/docs/http/ngx_http_rewrite_module.html#rewrite

Caddy

https://caddyserver.com/docs/caddyfile/matchers