← back to v142 · compression-dictionary-ttl
conformance · v142
v142 · compression-dictionary-ttl — conformance probe
7 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
7
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
use-as-dictionary-ttl-zero-token |
Use-As-Dictionary can carry an explicit ttl=0 parameter. spec ↗ | script | … | |
ttl-zero-immediately-expires |
ttl=0 makes a dictionary ineligible for subsequent requests even when no time has elapsed. spec ↗ | script | … | |
ttl-shorter-than-cache-control |
An explicit ttl can expire dictionary usefulness before the HTTP cache max-age expires. spec ↗ | script | … | |
ttl-outlives-cache-control |
An explicit ttl can keep dictionary usefulness separate from the resource's HTTP cache lifetime. spec ↗ | script | … | |
omitted-ttl-follows-cache-lifetime |
When ttl is omitted, the fallback model follows the HTTP cache lifetime. spec ↗ | script | … | |
available-dictionary-only-when-fresh |
The Available-Dictionary request header is only modeled when the selected dictionary lifetime is fresh. spec ↗ | script | … | |
dcb-dcz-content-codings-preserved |
Headers can preserve the dcb and dcz content-coding tokens used when a fresh dictionary is available. spec ↗ | script | … |