Strips the Referer header down to an origin when it's size exceeds 4k.
As noted in https://github.com/xsleaks/xsleaks/wiki/Browser-Side-Channels#cache-and-error-events, servers will often behave in unexpected ways when presented with an overly-long `Referer` header. This is unfortunate, as `Referer` is one header whose length attackers generally retain control over when generating `no-cors` requests.
Specification being incubated in a Community Group
Status in Chromium
Enabled by default
Consensus & Standardization
- No signal
- No signals
Last updated on 2021-12-13