Skip to main content

How to fix: Legacy Pragma Header Used

Pragma: no-cache header present.

Why it matters

Legacy header, HTTP/1.0 only.

Cache-Control is preferred for HTTP/1.1+.

How to fix it

  1. 1Use Cache-Control instead of Pragma.

Code examples

Replace Pragma: no-cache with Cache-Control

JavaScript
// Pragma: no-cache is a HTTP/1.0 artifact, use Cache-Control for modern browsers
// Remove Pragma header and use:
// next.config.mjs
export default {
  async headers() {
    return [{ source: "/(.*)", headers: [{ key: "Cache-Control", value: "no-store, max-age=0" }] }];
  },
};

References

Detected automatically by VulnRadar. The check id is pragma-no-cache-legacy, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Legacy Pragma Header Used?
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 pragma-no-cache-legacy, 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 legacy pragma header used

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: Legacy Pragma Header Used | VulnRadar