The fastest cache hit is one that never executes PHP. Modern caching plugins serve static files directly via web-server rules (Apache mod_rewrite in wp-content/cache/.htaccess, nginx try_files) and use the advanced-cache.php drop-in only as fallback.
WP Recache stores flat md5(host+path).html files — opaque hashes make rewrite-rule serving impossible, so every hit costs a PHP process.
Activation writes mod_rewrite rules serving those files when present (with logged-in-cookie and query-string conditions); nginx documented via try_files snippet
Human-inspectable paths; purge-by-URL = delete one directory
Drop-in remains as fallback for non-Apache servers
Note: supersedes the md5 layout introduced in the Phase 1 collision fix; both solve collisions, but only the directory layout enables static serving.
The fastest cache hit is one that never executes PHP. Modern caching plugins serve static files directly via web-server rules (Apache mod_rewrite in wp-content/cache/.htaccess, nginx try_files) and use the advanced-cache.php drop-in only as fallback.
WP Recache stores flat md5(host+path).html files — opaque hashes make rewrite-rule serving impossible, so every hit costs a PHP process.
**Spec:**
- Cache layout becomes cache/wp-recache/{host}{uri}/index(-mobile).html
- Activation writes mod_rewrite rules serving those files when present (with logged-in-cookie and query-string conditions); nginx documented via try_files snippet
- Human-inspectable paths; purge-by-URL = delete one directory
- Drop-in remains as fallback for non-Apache servers
**Note:** supersedes the md5 layout introduced in the Phase 1 collision fix; both solve collisions, but only the directory layout enables static serving.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The fastest cache hit is one that never executes PHP. Modern caching plugins serve static files directly via web-server rules (Apache mod_rewrite in wp-content/cache/.htaccess, nginx try_files) and use the advanced-cache.php drop-in only as fallback.
WP Recache stores flat md5(host+path).html files — opaque hashes make rewrite-rule serving impossible, so every hit costs a PHP process.
Spec:
Note: supersedes the md5 layout introduced in the Phase 1 collision fix; both solve collisions, but only the directory layout enables static serving.