wp-rocket-cache-rejection-and-filters

To exclude URIs from WP Rocket caching, apply the rocket_cache_reject_uri filter with path patterns in a companion plugin. This prevents specific page requests from being cached while keeping the rest of the site fully cached.

Yes, you can gate WP Rocket caching for cookies and user agents using the rocket_cache_reject_cookies filter. This allows per-visitor experiences by ensuring requests with specific cookies or user agents bypass the cache entirely.

You rewrite CDN URLs by applying the rocket_cdn_cnames filter to manage asset handling. This allows you to define CDN CNAMEs and fine-tune how asset URLs are rewritten across your WordPress site.

The safest way to customize lazy-load and asset handling is using feature-detection and prioritized rocket_* filters. This approach safely extends WP Rocket functionality without breaking site compatibility during activation.

You should exclude REST API endpoints from WP Rocket caching when handling dynamic or per-visitor data that must bypass the cache. Applying targeted cache rejection filters ensures REST responses remain uncached and accurate.