Clear-Site-Data header clears browsing data (cookies, storage, cache) associated with the requesting website. It allows web developers to have more control over the data stored locally by a browser for their origins.
|Header type||Response header|
|Forbidden header name||no|
Clear-Site-Data header accepts one or more directives. If all types of data should be cleared, the wildcard directive (
"*") can be used.
// Single directive Clear-Site-Data: "cache" // Multiple directives (comma separated) Clear-Site-Data: "cache", "cookies" // Wild card Clear-Site-Data: "*"
All directives must comply with the quoted-string grammar. A directive that does not include the double quotes is invalid.
- Indicates that the server wishes to remove locally cached data (i.e. the browser cache, see HTTP caching) for the origin of the response URL. Depending on the browser, this might also clear out things like pre-rendered pages, script caches, WebGL shader caches, or address bar suggestions.
- Indicates that the server wishes to remove all cookies for the origin of the response URL. HTTP authentication credentials are also cleared out. This affects the entire registered domain, including subdomains. So https://example.com as well as https://stage.example.com, will have cookies cleared.
- Indicates that the server wishes to remove all DOM storage for the origin of the response URL. This includes storage mechanisms such as:
- localStorage (executes
- sessionStorage (executes
- IndexedDB (for each database execute
- Service worker registrations (for each service worker registration, execute
- WebSQL databases,
- FileSystem API data,
- Plugin data (Flash via
- localStorage (executes
- Indicates that the server wishes to reload all browsing contexts for the origin of the response (
- Indicates that the server wishes to clear all types of data for the origin of the response. If more data types are added in future versions of this header, they will also be covered by it.
If a user signs out of your website or service, you might want to remove locally stored data. You can achieve that by adding the
Clear-Site-Data header when sending the page confirming that logging out from the site has been accomplished successfully (https://example.com/logout, for example):
Clear-Site-Data: "cache", "cookies", "storage", "executionContexts"
If this header is delivered with the response at https://example.com/clear-cookies, all cookies on the same domain https://example.com and any subdomains (like https://stage.example.com, etc), will be cleared out.
|Clear Site Data |
BCD tables only load in the browser