• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question How to use Clear-Site-Data header rule to clear browser cache

AntoineW

New Pleskian
Server operating system version
Debian 10.13
Plesk version and microupdate number
Plesk Obsidian v18.0.57
Hello,

I try to add Clear-Site-Data rule to the header of a domain, without success.


Here are the Apache cutoms header rules I have :

Code:
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
Strict-Transport-Security: max-age=31536000
X-XSS-Protection: "1; mode=block"
Feature-Policy: vibrate 'self'; usermedia *;
Cache-Control: no-cache
Clear-Site-Data: "cache"

Image1.jpg

HTML page has those META :

Code:
<meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate">
<meta http-equiv="Pragma" content="no-cache">
<meta http-equiv="Expires" content="0">

This doesn't seem to work: if a user initially had the HTML page cached in its browser, the directive does not clear its cache.

Test has been done with Google Chrome on client side.
Debian Plesk Obsidian v18.0.57 on server side.

I'm probably making a mistake somewhere.

Thanks for help.
 
Did you check if the header is actually present in your browser when you visit your domain?
 
Back
Top