Integrations / Cache
WP Rocket security with Stack Guard
Page caches keep the headers a page had when it was stored, and a cached sign-in page breaks sign-in protection. Stack Guard detects WP Rocket, checks your sign-in page is not cached, and clears WP Rocket's cache after a restore.
What Stack Guard checks
WP Rocket security: what Stack Guard checks
Cache detected
Stack Guard names WP Rocket and reminds you to exclude the sign-in address and clear the cache after changing security headers.
Sign-in page test
A real request to your sign-in page shows whether any cache is serving it.
Cleared after a restore
When you restore a backup, Stack Guard asks WP Rocket to clear its cache so visitors see the restored site.
Recommended settings for WP Rocket
- Exclude your custom sign-in address from caching.
- Clear the cache after changing security headers.
Read more in the docs
Questions
WP Rocket and Stack Guard: questions
Does WP Rocket conflict with a custom login URL?
Only if the sign-in page is cached. Exclude it in WP Rocket, and Stack Guard's sign-in page test confirms it is served fresh.
Why clear the cache after changing security headers?
Cached pages keep the headers they were stored with, so new headers only appear once the cache is cleared.
More integrations
WP Rocket is a trademark of its owner. Stack Guard is not affiliated with or endorsed by it.
Protect your WP Rocket site free
Install Stack Guard Free and open the compatibility check. It takes a minute.