How To Keep Sign-in Pages Out of Caches With BetterShield?
Tells caching plugins, server caches and CDNs not to keep a copy of the sign-in page. No files change.
With BetterShield, tells caching plugins, server caches and CDNs not to keep a copy of the sign-in page. No files change.
What it does
Sign-in page cache protection is under BetterShield › Protection › Hardening. Tells caching plugins, server caches and CDNs not to keep a copy of the sign-in page. No files change. It is off by default.
Step 1: Open Protection › Hardening
Open Protection › Hardening and find Sign-in page cache protection.
Step 2: Keep sign-in pages out of caches
- Open its preview and read what will change. The preview changes nothing.
- There are no extra fields. The fix tells compatible page caches, servers and CDNs not to cache the sign-in page.
- Turn on the fix. If the screen asks you to confirm recovery or your password, complete that before continuing.
Recommended settings
Our advice is to test this on staging, then apply it when the behavior fits the site. Keep a working recovery method before changes affecting sign-in or the site address.
What it can break and how to undo
A cache that ignores these instructions still needs a sign-in exclusion in its own settings. Check the response after enabling it. Turn the fix off to use its undo, then check the original workflow. A change is recorded in the activity log; an undo does not erase that record.
Final Outcome
The row should show the fix is on. Test the affected operation with an appropriate account, then check the finding. The score and Findings update on their own after the change. If the finding stays open, press Check Again to see what the check still sees. A server or another plugin can enforce a setting independently, so switching BetterShield off does not necessarily remove that other protection.
Related
This is how you can keep sign-in pages out of caches with BetterShield.
Getting Stuck? Feel free to contact our Dedicated Support Team.