Draft
This page is not complete.
The Sec-Fetch-User fetch metadata header indicates whether or not a navigation request was triggered by a user activation.
| Header type | Fetch Metadata Request Header |
|---|---|
| Forbidden header name | yes, since it has prefix Sec- |
| CORS-safelisted request header |
Syntax
Sec-Fetch-User: ?0 Sec-Fetch-User: ?1
Values
The value is a Boolean Structured Header.
?0- The navigation request was triggered by a user activation.
?1- The navigation request was triggered by something other than a user activation.
Examples
TODO
Specifications
| Specification | Title |
|---|---|
| Fetch Metadata Request Headers | The Sec-Fetch-User HTTP Request Header |
Browser compatibility
The compatibility table on this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
Update compatibility data on GitHub
| Desktop | Mobile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sec-Fetch-User | Chrome Full support 76 | Edge Full support 79 | Firefox No support No | IE No support No | Opera Full support 63 | Safari No support No | WebView Android Full support 76 | Chrome Android Full support 76 | Firefox Android No support No | Opera Android Full support 54 | Safari iOS No support No | Samsung Internet Android No support No |
Legend
- Full support Â
- Full support
- No support Â
- No support
- Experimental. Expect behavior to change in the future.
- Experimental. Expect behavior to change in the future.