Merge branch 'main' into dht

Author: lidel

.github/workflows/build.yml

@@ -51,4 +51,5 @@ jobs:
         with:
           name: website-build-${{ github.run_id }}
           path: ${{ env.BUILD_PATH }}
-          retention-days: 1
+          retention-days: 1
+          include-hidden-files: true

.github/workflows/linter.yml

@@ -14,7 +14,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout Code
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           # Full git history is needed to get a proper list of changed files within `super-linter`
           fetch-depth: 0

.markdownlint.json

@@ -9,5 +9,6 @@
   "single-trailing-newline": false,
   "link-fragments": false,
   "line-length": false,
-  "blanks-around-fences": false
+  "blanks-around-fences": false,
+  "no-inline-html": false
 }

Makefile

@@ -12,6 +12,7 @@ install:
 
 website: clean install
 	npx spec-generator -c .config.json
+	touch out/.nojekyll
 
 watch: clean install
 	npx spec-generator -c .config.json -w

package-lock.json

@@ -9,7 +9,7 @@
   "author": "",
   "license": "",
   "private": true,
-  "devDependencies": {
-    "spec-generator": "^1.6.0"
+  "dependencies": {
+    "spec-generator": "^1.6.1"
   }
 }

package.json

@@ -18,6 +18,9 @@ editors:
         url: https://protocol.ai/
 tags: ['architecture']
 order: 0
+xref:
+  - trustless-gateway
+  - http-routing-v1
 ---
 
 The IPFS stack is a suite of specifications and tools that share two key characteristics:

src/architecture/principles.md

@@ -17,6 +17,9 @@ editors:
     affiliation:
       name: Cloudflare
       url: https://cloudflare.com/
+xref:
+  - path-gateway
+  - web-redirects-file
 tags: ['httpGateways', 'webHttpGateways']
 order: 4
 ---

src/http-gateways/dnslink-gateway.md

@@ -16,6 +16,7 @@ editors:
       name: Shipyard
       url: https://ipshipyard.com
 xref:
+  - http-routing-v1
   - path-gateway
   - trustless-gateway
 tags: ['httpGateways', 'lowLevelHttpGateways', 'exchange', 'transport']

src/http-gateways/libp2p-gateway.md

@@ -4,15 +4,23 @@ description: >
   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.
-date: 2024-04-17
+date: 2025-10-13
 maturity: reliable
 editors:
   - name: Marcin Rataj
     github: lidel
     url: https://lidel.org/
     affiliation:
-      name: Protocol Labs
-      url: https://protocol.ai/
+      name: Shipyard
+      url: https://ipshipyard.com
+former_editors:
+  - name: Henrique Dias
+    github: hacdias
+    url: https://hacdias.com/
+    affiliation:
+      name: Shipyard
+      url: https://ipshipyard.com
+thanks:
   - name: Adrian Lanzafame
     github: lanzafame
     affiliation:
@@ -28,17 +36,15 @@ editors:
     affiliation:
       name: Protocol Labs
       url: https://protocol.ai/
-  - name: Henrique Dias
-    github: hacdias
-    url: https://hacdias.com/
-    affiliation:
-      name: Protocol Labs
-      url: https://protocol.ai/
 xref:
   - url
   - trustless-gateway
+  - subdomain-gateway
+  - dnslink-gateway
   - ipip-0402
   - ipip-0412
+  - ipip-0288
+  - ipns-record
 tags: ['httpGateways', 'lowLevelHttpGateways']
 order: 0
 ---
@@ -328,6 +334,11 @@ Gateways MUST use 404 to signal that content is not available, particularly
 when the gateway is [non recursive](#recursive-vs-non-recursive-gateways), and only provides access to a known
 dataset, so that it can assess that the requested content is not part of it.
 
+NOTE: Gateways MUST return 404 for missing root blocks. However, for streaming
+responses (such as CAR), once HTTP 200 OK status is sent, gateways cannot
+change it. If a child block is missing during streaming, the gateway SHOULD
+terminate the stream. Clients MUST verify response completeness.
+
 ### `410` Gone
 
 Error to indicate that request was formally correct, but this specific Gateway
@@ -635,6 +646,10 @@ Indicates the original, requested content path before any path resolution and tr
 
 Example: `X-Ipfs-Path: /ipns/k2..ul6/subdir/file.txt`
 
+This header SHOULD be returned with deserialized responses.
+Implementations MAY omit it with trustless response types
+(`application/vnd.ipld.raw` and `application/vnd.ipld.car`).
+
 ### `X-Ipfs-Roots` (response header)
 
 Used for HTTP caching.
@@ -664,6 +679,15 @@ NOTE: while the first CID will change every time any article is changed,
 the last root (responsible for specific article or a subdirectory) may not
 change at all, allowing for smarter caching beyond what standard Etag offers.
 
+This header SHOULD be returned with deserialized responses.
+Implementations MAY omit it with trustless response types
+(`application/vnd.ipld.raw` and `application/vnd.ipld.car`).
+
+NOTE: Gateways that stream responses (e.g., CAR) without pre-resolving the
+entire path MAY only include the root CID for simple `/ipfs/{cid}` requests, or
+MAY omit this header for path requests where intermediate CIDs are not known
+when headers are sent.
+
 ### `X-Content-Type-Options` (response header)
 
 Optional, present in certain response types: