www.ipfs.io doesn't resolve

[jesseclay]

some redirect weirdness here... more of an edge case than anything but should be fixed.

[ghost]

Good suggestion, we don't have that subdomain set at all. We should probably also set it for all the other sites? I imagine we'd have a bit of nginx config which redirects to the non-www version.

[victorb]

Think we're using dnslink for deploying ipfs.io, so easiest would be to just add another record and update deploy commands in https://github.com/ipfs/website/blob/master/Makefile#L95 to include new record as well.

[jbenet]

it would be nice to -- where possible -- redirect to remove the www. prefix. it's just outdated.

[ghost]

Uggh I don't know, then we'll also have to have www.ipfs.io/ipfs and /ipns -- and support it forever

[ghost]

redirect to remove the www. prefix. it's just outdated.

and agree to that

[jbenet]

and support it forever

ooof yeah-- that would suck. :)

[ghost]

In the case of the redirect, we might want to consider having it only with a fixed set of domains, and not for everything that starts in www. People might legitimately have their www. domain pointed to the gateway. On the other hand, they might not, and in that case it would be useful to remove it, mh. This is essentially /ipns/example.com and /ipns/www.example.com.

Maybe this opens up space for a generic www-removal in go-ipfs-gateway itself, where we try to look up a dnslink for the www-version, and redirect to nowww if there's none. This means we'd still pick up the dnslink if the owner of the domain legitimately is using the www-version.

[ghost]

Hehe funny how github turns just www. into a hyperlink.

[jbenet]

@lgierth agree with your above proposal.

And, woah the link www. works where I'm at today:

[victorb]

Resolved to http://www.www.com/ for me in Firefox

Links...

[ghost]

This is tracked in ipfs/go-ipfs-gateway#7