Kevin Wallace 084cdc3ed8 gateway: attempt to resolve hostname to ipfs path ... This allows someone to host a static site by pointing a TXT record at their content in IPFS, and a CNAME record at an IPFS gateway. Note that such a setup technically violates RFC1912 (section 2.4; "A CNAME record is not allowed to coexist with any other data."), but tends to work in practice. We may want to consider changing the DNS->IPFS resolution scheme to allow this scenario to be RFC-compliant (e.g. store the mapping on a well-known subdomain to allow CNAME records on the domain itself). License: MIT Signed-off-by: Kevin Wallace <kevin@pentabarf.net>		2015-02-08 11:27:06 -08:00
..
commands.go	corehttp: ServeOption supports chaining muxes	2015-02-08 11:27:06 -08:00
corehttp.go	corehttp: ServeOption supports chaining muxes	2015-02-08 11:27:06 -08:00
gateway_handler.go	gateway: dont cache ipns paths	2015-02-07 10:10:05 -08:00
gateway.go	corehttp: ServeOption supports chaining muxes	2015-02-08 11:27:06 -08:00
ipns_hostname.go	gateway: attempt to resolve hostname to ipfs path	2015-02-08 11:27:06 -08:00
redirect.go	corehttp: ServeOption supports chaining muxes	2015-02-08 11:27:06 -08:00
webui.go	corehttp: allow all webui paths we published.	2015-02-06 07:30:42 -08:00