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

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

This release was brought to you by the Shipyard team.

v0.8.1

Changed

• DAG-CBOR HTML preview pages previously had to be returned without Cache-Control headers. Now they can use Cache-Control headers similar to those used in generated UnixFS directory listings. #241

This release was brought to you by the Shipyard team.

v0.8.0

Changed

• Comprehensive tests for HTTP Range Requests over deserialized UnixFS files have been added. The --specs path-gateway now 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.

v0.7.1

Changed

• Expect all URL escapes to use uppercase hex #232

This release was brought to you by the Shipyard team.

v0.7.0

Changed

• Update dependencies #226 and #227
• Expect upper-case hex digits in escaped redirect URL #225

This release was brought to you by the Shipyard team.

v0.6.2

Changed

• Relaxed negative test of TAR response #221

This release was brought to you by the Shipyard team.

v0.6.1

Changed

• Support meaningful Cache-Control on generated UnixFS directory listing responses on /ipfs namespace #219

This release was brought to you by the Shipyard team.

v0.6.0

Changed

• Gateway URL
  • --gateway-url is no longer defaulting to predefined URL. User has to provide it via CLI or GATEWAY_URL environment variable or the test suite will refuse to start.
  • This aims to ensure no confusion about which gateway endpoint is being tested.
  • Docs and examples use --gateway-url http://127.0.0.1:8080 to ensure no confusion with localhost:8080 subdomain gateway feature in IPFS implementations like Kubo.
• Subdomain URL and UX related to subdomain tests
  • The --subdomain-url is no longer set by default.
  • User has to provide the origin of the subdomain gateway via CLI or SUBDOMAIN_GATEWAY_URL to be used during subdomain tests. This aims to ensure no confusion about which domain name is being tested.
  • Simplified the way --subdomain-url works. We no longer run implicit tests against http://localhost in addition to the URL passed via --subdomain-url. To test more than one domain, run test multiple times.
  • localhost subdomain gateway tests are no longer implicit. To run tests against localhost use --subdomain-url http://localhost:8080
• DNSLink test fixtures changed
  • DNSLink fixtures no longer depend on --subdomain-url and use unrelated *.example.org domains instead.
  • gateway-conformance extract-fixtures creates dnslinks.IPFS_NS_MAP with content that can be directly set as IPNS_NS_MAP environment variable supported by various implementations, incl. Kubo and Rainbow.
• Docker: image can now be run under non-root user
• HTTP Proxy tests are no longer implicit. An explicit spec named proxy-gateway exists now, and can be disabled via --specs -proxy-gateway.

This release was brought to you by the Shipyard team.

v0.5.2

Changed

• Fixed: relaxed dag-cbor error check (#205)
• Fixed: Header().Has works properly for checking multiple values (#207)

This release was brought to you by the Shipyard team.