Skip to main content
InfoHeadersOWASP A05:2021CWE-693

How to fix: Origin-Agent-Cluster Has an Invalid Value

The Origin-Agent-Cluster header is present but set to a value other than the two the spec defines, '?1' or '?0', so browsers discard it and treat the header as if it were never sent.

Why it matters

Because the value fails to parse as the structured boolean the spec expects, the page still lands in the browser's default agent cluster, the exact outcome the developer was presumably trying to opt out of by sending this header at all.

Origin-Agent-Cluster is a Structured Header boolean and only recognizes the literal tokens '?1' (request origin-keyed isolation) and '?0' (explicitly opt out, preserving document.domain relaxation). Any other value, including 'true', '1', or 'yes', fails to parse and is silently discarded by the browser.

How to fix it

  1. 1Set Origin-Agent-Cluster to exactly '?1' to request origin-keyed isolation, or '?0' to explicitly opt out.
  2. 2Double-check the header is sent as a raw string value, not JSON-encoded or wrapped in extra quotes by a proxy or framework.

Code examples

Next.js

JavaScript
// next.config.mjs
export default {
  async headers() {
    return [{ source: "/(.*)", headers: [{ key: "Origin-Agent-Cluster", value: "?1" }] }];
  },
};

References

Detected automatically by VulnRadar. The check id is origin-agent-cluster-invalid-value, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Origin-Agent-Cluster Has an Invalid Value?
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 origin-agent-cluster-invalid-value, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Origin-Agent-Cluster Has an Invalid Value map to?
It maps to CWE-693. In the OWASP Top 10 it falls under A05:2021.

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 origin-agent-cluster has an invalid value

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

Origin-Agent-Cluster Has an Invalid Value fix | VulnRadar