Releases: ipfs/gateway-conformance
Releases · ipfs/gateway-conformance
v0.7.1
v0.7.0
v0.6.2
v0.6.1
v0.6.0
Changed
- Gateway URL
--gateway-url
is no longer defaulting to predefined URL. User has to provide it via CLI orGATEWAY_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 withlocalhost: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 againsthttp://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 againstlocalhost
use--subdomain-url http://localhost:8080
- The
- DNSLink test fixtures changed
- DNSLink fixtures no longer depend on
--subdomain-url
and use unrelated*.example.org
domains instead. gateway-conformance extract-fixtures
createsdnslinks.IPFS_NS_MAP
with content that can be directly set asIPNS_NS_MAP
environment variable supported by various implementations, incl. Kubo and Rainbow.
- DNSLink fixtures no longer depend on
- 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
.