annevk
commented
11 months ago It seems the intent is for this to be only available to top-level documents, although how that works exactly looks a bit sketchy (there's no relevant settings object of nothing). Anyway, that explains why it being keyed solely on origin is not necessarily bad.
A more complete analysis of this is blocked on #20.
WebKittens
@annevk
Title of the spec
Clear Client Hints via Clear-Site-Data header
URL to the spec
https://w3c.github.io/webappsec-clear-site-data/
URL to the spec's repository
https://github.com/w3c/webappsec-clear-site-data/issues/new
Issue Tracker URL
https://crbug.com/1458394
Explainer URL
https://groups.google.com/a/chromium.org/g/blink-dev/c/lJY86eTPQ0s/
TAG Design Review URL
https://github.com/w3ctag/design-reviews/issues/871
Mozilla standards-positions issue URL
https://github.com/mozilla/standards-positions/issues/848
WebKit Bugzilla URL
No response
Radar URL
No response
Description
Websites will now be able to clear the client hints cache using
Clear-Site-Data: “clientHints”. Client hints will also now be cleared when “cookies”, “cache”, or “*” are targeted by the same header. This is because if the user clears cookies in the UI client hints are already cleared as well, the client hints cache is a cache, and to be consistent with wildcard targets respectively.