HTTP Gateways

IPFS Gateway acts as a bridge between traditional HTTP clients and IPFS. Through the gateway, users can download files, directories and other IPLD data stored in IPFS as if they were stored in a traditional web server.

HTTP

Low-level gateways that expose IPFS resources over HTTP protocol.

Path Gateway Specification
The comprehensive low-level HTTP Gateway enables the integration of IPFS resources into the HTTP stack through /ipfs and /ipns namespaces, supporting both deserialized and verifiable response types.
Trustless Gateway Specification
The minimal subset of HTTP Gateway response types facilitates data retrieval via CID and ensures integrity verification, all while eliminating the need to trust the gateway itself.
libp2p+HTTP Transport Gateway Specification
Describes how HTTP Gateway semantics can be used over libp2p transports.

Web

Designed for website hosting and improved interoperability with web browsers and origin-based security model.

Subdomain Gateway Specification
Defines how HTTP Gateway can implement support for HTTP Host headers to enable isolated website hosting based on root CID-derived Origins. This ensures compatibility with native ipfs:// and ipns:// URIs, and aligns with the existing Same-origin security model in web browsers, including relative URL pathing and permission scopes of Web APIs.
DNSLink Gateway Specification
Defines how to utilize the HTTP Host header to serve a content path from a DNSLink record as a website under a particular DNS name.
Web _redirects File Specification
Defines how URL redirects and rewrites can be implemented by adding rules to a plain text file stored underneath the root CID of a website.