Skip to main content

How to fix: Expires Header Set to Past

Expires header set to date in the past.

Why it matters

Signals no caching to legacy proxies.

Past expiry prevents legacy caching.

How to fix it

  1. 1Use Cache-Control for modern caching control.

Code examples

Remove Expires headers or set Cache-Control instead

JavaScript
// Expires header with a past date is a HTTP/1.0 mechanism, use Cache-Control
// For no caching:
// next.config.mjs
export default {
  async headers() {
    return [{ source: "/(.*)", headers: [{ key: "Cache-Control", value: "no-store, max-age=0" }] }];
  },
};
// For long caching of static assets:
// Cache-Control: public, max-age=31536000, immutable

References

Detected automatically by VulnRadar. The check id is expires-past, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Expires Header Set to Past?
VulnRadar rates this info severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id expires-past, which stays the same between runs so you can filter, diff, or gate CI on it.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for expires header set to past

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Expires Header Set to Past | VulnRadar