mirror of https://github.com/ipfs/kubo.git synced 2026-02-23 11:27:42 +08:00

Steven Allen d5f67d5d7e fix the default gateway port

reported by @sixcorners in
https://github.com/ipfs/go-ipfs/pull/5393#issuecomment-417908209

License: MIT
Signed-off-by: Steven Allen <steven@stebalien.com>

2018-09-02 09:37:43 -07:00

1.8 KiB

Raw Blame History

Gateway

An IPFS Gateway acts as a bridge between traditional web browsers and IPFS. Through the gateway, users can browse files and websites stored in IPFS as if they were stored in a traditional web server.

By default, go-ipfs nodes run a gateway at http://127.0.0.1:8080/.

We also provide a public gateway at https://ipfs.io. If you've ever seen a link in the form https://ipfs.io/ipfs/Qm..., that's being served from our gateway.

Configuration

The gateway's configuration options are (briefly) described in the config documentation.

Directories

For convenience, the gateway (mostly) acts like a normal web-server when serving a directory:

If the directory contains an index.html file:
If the path does not end in a /, append a / and redirect. This helps avoid serving duplicate content from different paths.^†
Otherwise, serve the index.html file.
Dynamically build and serve a listing of the contents of the directory.

_{^†This redirect is skipped if the query string contains a
go-get=1 parameter. See PR#3964
for details}

Filenames

When downloading files, browsers will usually guess a file's filename by looking at the last component of the path. Unfortunately, when linking directly to a file (with no containing directory), the final component is just a CID (Qm...). This isn't exactly user-friendly.

To work around this issue, you can add a filename=some_filename parameter to your query string to explicitly specify the filename. For example:

https://ipfs.io/ipfs/QmfM2r8seH2GiRaC4esTjeraXEachRt8ZsSeGaWTPLyMoG?filename=hello_world.txt

MIME-Types

TODO

1.8 KiB Raw Blame History