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.
IPIP-518: URIs in Routing V1 API via Generic Schema by lidel · Pull Request #518 · ipfs/specs
This IPIP extends /routing/v1 HTTP API to allow HTTP(S) URLs alongside multiaddrs in Addrs field in a new Record type defined by Schema=generic. Rationale in the IPIP document, TLDR is that allowin...
Special-Use Domain Names
This document describes what it means to say that a Domain Name (DNS name) is reserved for special use, when reserving such a name is appropriate, and the procedure for doing so. It establishes an IANA registry for such domain names, and seeds it with entries for some of the already established special domain names.
Theme: Non-DNS origin definitions · Issue #12 · webtransitions/initiatives
An "origin" as defined by web standards and implemented by the major browser engines today anchors user trust decisions in the originating website publisher information, and delivered via...
localhost subdomains do not work on Safari (macOS) · Issue #206 · ipfs/in-web-browsers
Version information: go-ipfs version: 0.6.0 Repo version: 10 System version: amd64/darwin Golang version: go1.14.4 Description: After 0.6.0 version local gateway started redirecting to localhost su...
IPFS is moving beyond the sponsored gateways
How IPFS is shifting from centralized public gateways to distributed infrastructure and client-side retrieval.
IPIP-504: `provider` query parameter as hint for HTTP Gateways by vasco-santos · Pull Request #504 · ipfs/specs
Based on initial exploration https://github.com/vasco-santos/provider-hinted-uri/blob/main/EXPLORATION.md
Introducing Filebase Sites: Simplified IPFS Websites with IPNS
Hosting a real website on IPFS has always come with friction: changing CIDs, manual IPNS management, and fragile workflows. Filebase Sites removes the last-mile complexity, giving developers a simple way to publish, update, and maintain decentralized websites without breaking links.
Content Identifiers (CIDs) | IPFS Docs
Learn about how content addressing works and how content identifiers, or CIDs, play a crucial role in IPFS.
HTTP Semantics
The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.
Browsers & Standards Work 2026: Call for Community Input
TL;DR: IPFS is planning the next phase of work to make browsers better for the decentralized web – not just IPFS, but any protocol that needs lightweight crypto, peer-to-peer connections, or native browser integration. We need your input on what features matters most. Background: What We’ve Accomplished Over the past 5 years, sustained collaboration with Igalia has delivered real improvements to all major browsers: Ed25519 in WebCrypto API - Shipped in Chrome 137 (May 2025), now available in...
Redirects and custom 404s | IPFS Docs
What the _redirect file is and how to use them with a website or single-page application (SPA) on IPFS.
README
This is a browser extension that provides “wormhole” navigation between different AT Protocol/Bluesky services inspired by Dame’s Shortcut. The extension transforms URLs and identifiers from one service to equivalent URLs on other services.
Substack writers, you need a website!
Substack is convenient, but treat it as a distribution tool for your content. Your content should live on an independently owned website, which has a domain name you control and own. This way, you …
Some Secret Management Belongs in Your HTTP Proxy - exe.dev blog
do third-party integrations via HTTP header management
I've been pondering about having the browser resolve at:// URLs. I have been thinking that we could introduce a DNS-like (maybe DNS itself?) entity that goes from did:plc to URLs, the same way DNS goes from names to IP, and have the browser depend on that similar to how it depends on a DNS server.
Important piece of multi-protocol support in browsers! Thanks to much work from Javi, and funding from @ipfs.tech. HEY NOW, settle down - a ways to go: - can only redirect to URLs/paths - no Safari - off by default in Chrome (for now) - only allow-listed schemes unprefixed Step by step...
Javier Fernandez
Blog post about a new Chromium feature I've been working on to allow Web Extensions register protocol handlers just declaring them in the Manifest. blogs.igalia.com/jfernandez/2026/03/24/protoco…
