The HTTP gateway included in go-ipfs will try to use a Host header on requests for constructing an /ipns path. So e.g. http://ipfs.io/docs http://ipfs.io/docs g

The HTTP gateway included in go-ipfs will try to use a Host header on requests for constructing an /ipns path. So e.g. http://ipfs.io/docs http://ipfs.io/docs gets turned into /ipns/ipfs.io/docs -- this is actually how we host all webpages within the ipfs project. edit: And the part which turns /ipns/ipfs.io into an /ipfs path is called dnslink: https://github.com/ipfs/go-dnslink https://github.com/ipfs/go-dnslink -- it resolves to what's in TXT _dnslink.ipfs.io. > (on a random note: what's up with /blog returning the IPFS blog, instead of my own content? did i misconfigure something?) I'm so sorry, that's a bug I put into the nginx configuration -- will fix it!