Releases: ipfs/gateway-conformance
Releases · ipfs/gateway-conformance
v0.10.1
Fixed
- Renamed
Base32Cid()toDNSSafeCidV1()and fixed it to convert CIDv0 to CIDv1 before encoding. Uses base36 forlibp2p-keycodec (IPNS keys) and base32 for everything else, producing valid DNS-safe CID strings for subdomain gateway tests. #264
Note
This release was brought to you by the Shipyard team.
v0.10.0
Changed
- IPIP-524: codec conversion tests now expect HTTP 406 Not Acceptable when the requested format does not match the block's native codec. Implementations supporting optional codec conversions for backward compatibility may skip these tests. #254
Note
This release was brought to you by the Shipyard team.
v0.9.0
v0.8.4
v0.8.3
Changed
- Added temporary support for legacy 200 with X-Stream-Error header behavior when missing blocks are detected during CAR streaming. This ensures compatibility with current boxo/gateway implementations that defer header setting. This third option will be removed once implementations ship with ipfs/boxo#1019. #245
Note
This release was brought to you by the Shipyard team.
v0.8.2
Changed
- Relaxed CAR tests to accept both HTTP 200 and 404 for non-existing paths. The response code now depends on implementation details such as locality and cost of path traversal checks. Implementations that can efficiently detect non-existing paths should return 404 (improved behavior per ipfs/boxo#458). Implementations focusing on stateless streaming and low latency may return 200 with partial CAR up to the missing link (legacy behavior). #244
Note
This release was brought to you by the Shipyard team.
v0.8.1
v0.8.0
Changed
- Comprehensive tests for HTTP Range Requests over deserialized UnixFS files have been added. The
--specs path-gatewaynow requires support for at least single-range requests. Deserialized range-requests can be skipped with--skip 'TestGatewayUnixFSFileRanges'#213 - Updated dependencies #236 & #239
This release was brought to you by the Shipyard team.

