http header
Sec-Fetch-Storage-Access header
The HTTP Sec-Fetch-Storage-Access fetch metadata request header provides the “storage access status” for the current fetch context.
The status can indicate that permission to access unpartitioned third-party cookies:
- Is not granted.
- Has been granted but not activated for the current request context.
- Has been granted for the current request content, and the cookies have been sent with the request.
Supporting browsers must include this header on cross-site requests when the request credential mode is include.
The header should not be sent with same-site requests (since those requests cannot involve cross-site cookies), or if the request’s credentials mode is “omit”.
The requested resource must also have a potentially trustworthy origin.
If a storage access permission has been granted but not activated, a server can respond with Activate-Storage-Access to request activation of the permission for the context.
For more information see Storage access headers in the Storage Access API overview.
| Header type | [Fetch Metadata Request Header](https://developer.mozilla.org/en-US/docs/Glossary/Fetch%20Metadata%20Request%20Header) |
|---|---|
| [Forbidden request header](https://developer.mozilla.org/en-US/docs/Glossary/Forbidden%20request%20header) | Yes (Sec- prefix) |
| [CORS-safelisted request header](https://developer.mozilla.org/en-US/docs/Glossary/CORS-safelisted%20request%20header) | No |
Syntax
Sec-Fetch-Storage-Access: none
Sec-Fetch-Storage-Access: inactive
Sec-Fetch-Storage-Access: active
Directives
A value indicating the storage access status for the current fetch context. The following values are allowed (servers should ignore other values):
none- : The context does not have the
storage-accesspermission or access to unpartitioned cookies.
- : The context does not have the
inactive- : The context has the
storage-accesspermission, but has not opted into using it (and does not have unpartitioned cookie access through other means). If this value is set, then theOriginrequest header should also be set.
- : The context has the
active- : The context has unpartitioned cookie access.
If this value is set, then the
Originrequest header should also be set.
- : The context has unpartitioned cookie access.
If this value is set, then the
Examples
See Examples in Activate-Storage-Access.
Specifications
Browser compatibility
See also
Activate-Storage-Access- Storage access headers in Storage Access API
- Storage access header sequences in Storage Access API
- Using the Storage Access API
- Fetch Metadata Request Headers playground (secmetadata.appspot.com)