feat: add ipfs.1-2.dev

[SoftCreatR]

n/t

[lidel]

@SoftCreatR it does not seem to work with IPNS (https://ipfs.1-2.dev/ipns/en.wikipedia-on-ipfs.org) – mind fixing?

[SoftCreatR]

Done. Took me some time, to figure out how to properly make it work in a subdomain environment. Would be nice if go-ipfs would handle the character replacements by it's own.

[lidel]

Thanks!

What do you mean by:

Would be nice if go-ipfs would handle the character replacements by it's own.
?

[SoftCreatR]

Thanks!

What do you mean by:

Would be nice if go-ipfs would handle the character replacements by it's own.
?

Replacing . by - and - by -- is somewhat, the Webserver shouldn't do by it's own, when using a subdomain setup. Since ipfs performs the redirect, it should also handle these rewrites.

[lidel]

Mind providing examples? Afaik go-ipfs does all redirects it can (without breaking TLS, as wildcart certs work only for a single label wildcard).

[SoftCreatR]

The one mentioned: https://ipfs.1-2.dev/ipns/en.wikipedia-on-ipfs.org

go-ipfs is configured for Subdomains, so what it does (or did during my tests) was to redirect to en.wikipedia-on-ipfs.org.ipfs.ipfs.1-2.dev, which isn't working due to the lack of wildcard cert depth.

[lidel]

I see. It sounds you are doing redirects from https://ipfs.1-2.dev/* to https://*.ipfs.1-2.dev/ subdomains at the level of some reverse proxy (nginx?), which is not smart enough to do necessary DNS label normalization.

Let go-ipfs handle https://ipfs.1-2.dev/* – it will do the redirect to proper https://*.ipfs.1-2.dev/ subdomain and do identifier normalization (if needed) so it works fine with TLS certs.

To be very specific, if you set X-Forwarded-Proto: https at your reverse proxy (before passing to go-ipfs), go-ipfs will take care of converting en.wikipedia-on-ipfs.org to the single label en-wikipedia--on--ipfs-org which will work with wildcard cert just fine.

See gateway recipes and examples at https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#gateway-recipes

[SoftCreatR]

It sounds you are doing redirects from https://ipfs.1-2.dev/* to https://*.ipfs.1-2.dev/ subdomains at the level of some reverse proxy (nginx?), which is not smart enough to do necessary DNS label normalization.

No, these redirects are handled by IPFS via proxy_pass http://gateway;, which works just fine, using this IPFS config:

"PublicGateways": {
  "*.1-2.dev": {
    "NoDNSLink": false,
    "Paths": [
      "/ipfs",
      "/ipns"
    ],
    "UseSubdomains": true
  }
},

After your request regarding IPNS, I've implemented this:

    location ~ ^/ipns/(?<name>.*) {
        rewrite_by_lua_block
        {
            local subdomain = ngx.var.name
            subdomain = string.gsub(subdomain, "%-", "--")
            subdomain = string.gsub(subdomain, "%.", "-")
            
            return ngx.redirect(ngx.var.scheme .. "://" .. subdomain .. ".ipns." .. ngx.var.host, 301)
        }
    }

which isn't by far not the most beautiful and convenient solution, but it works so far.

What I didn't know was, that proxy_set_header X-Forwarded-Proto https simply does the trick. So I've removed the lua part and simply added that line and it works, as expected :)