Introduces a new set of HTTP request headers, including `Sec-Fetch-Site`, `Sec-Fetch-Mode` and `Sec-Fetch-User`, that sends additional metadata about a request's provenance (is it cross-site, is it triggered from <img>, etc.) to the server to allow it to make security decisions which might mitigate some kinds of attacks based on timing the server's response (xsleaks and others).
Specification
Status in Chromium
Enabled by default (tracking bug) in:
- Chrome for desktop release 76
- Chrome for Android release 76
- Android WebView release 76
Consensus & Standardization
After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.
- No signal
- No signal
- No signal
- Positive
Owner
Intent to Prototype url
Intent to Prototype threadLast updated on 2020-12-25
Comments
For example, it's unlikely that a bank's "Transfer all money" endpoint would be referenced from an img tag, and likewise unlikely that evil.com is going to be making any legitimate requests whatsoever. Ideally, the server could reject these requests a priori rather than deliver them to the application backend.