A sampled build-like asset response had an explicitly uncached Cache-Control signal
ShipReady found one sampled build-like script or stylesheet response with no Cache-Control, no-cache, no-store, or max-age=0.
Why it matters
A cache policy on a versioned asset can be reviewed against the deployment’s invalidation strategy.
How ShipReady detects it
What it inspects
ShipReady extracts static script and stylesheet URLs with recognized build-directory or hashed-filename patterns, then safely probes eligible URLs with streamed redirect-following requests.
What triggers a finding
From the first usable HTTP 200 response among up to five candidates, it triggers when Cache-Control is absent or contains no-cache, no-store, or max-age=0.
What the evidence shows
The evidence proves the reported sampled asset returned the shown Cache-Control value during the scan.
Limits of this check
Only recognized static script and stylesheet paths are candidates. Unsafe URLs, non-200 responses, and unavailable requests are not findings; no usable response is incomplete.
The first usable asset decides this rule. ShipReady does not inspect every asset, verify immutability, measure browser cache behavior, inspect intermediaries, or establish returning-visitor cost.
How to fix it
Review the observed evidence
Confirm the asset is intentionally versioned and choose a policy compatible with deployment invalidation.
How to verify the change
Verify the intended behavior
Inspect deployed asset headers after the policy change.
Expected: The intended asset returns the selected Cache-Control policy.