https:\/\/www.youtube.com\/watch?v=WEbKAD3ByMg<\/p>\n\n
Most page caches store one copy of a page. That breaks every site that renders a page differently per country: a WooCommerce shop that shows prices including the VAT rate of the visitor's country, or a site that sends first-time visitors from abroad to its English version. Cache such a site and every visitor sees the prices of whoever happened to fill the cache.<\/p>\n\n
Wonderful Geo Page Cache<\/strong> keeps a separate copy per visitor country, looked up from the GeoLite2-Country database WooCommerce already maintains, and per value of the cookies you name. A visitor from Germany gets the copy rendered for Germany, a visitor from Austria the one for Austria \u2014 and bots and scanners, who hit the same pages over and over, cost about a millisecond instead of a full WordPress render.<\/p>\n\n From a GeoLite2-Country database on your server. If WooCommerce geolocation is enabled, its database is used automatically; otherwise enter the path of any MaxMind DB file. Nothing is sent to an external service.<\/p><\/dd>\n If the web server already puts the client address into The prewarmer requests the page from the site itself with a header signed by a key derived from the salts in In No. Only one plugin can own What makes it different<\/h4>\n\n
\n
How it works<\/h4>\n\n
\n
advanced-cache.php<\/code> drop-in answers cached requests before WordPress loads.<\/li>\n\n
define( 'WP_CACHE', true );<\/code> to wp-config.php<\/code>.<\/li>\nX-Wonderful-Geo-Page-Cache<\/code> says MISS<\/code> on the first request and HIT<\/code> on the next one.<\/li>\n<\/ol>\n\n\n\n
Where does the country come from?<\/h3><\/dt>\n
My server sits behind a proxy.<\/h3><\/dt>\n
REMOTE_ADDR<\/code> (mod_remoteip, as in the official WordPress Docker image), keep REMOTE_ADDR<\/code> \u2014 mod_remoteip removes the forwarded header it has read. Otherwise choose the header that carries the client address (for example HTTP_X_FORWARDED_FOR<\/code>). If the configured source is missing on a request, that request is not cached rather than filed under an unknown country.<\/p><\/dd>\nHow does prewarming render a page for another country?<\/h3><\/dt>\n
wp-config.php<\/code>, which only the site knows and which is never written to a file. The drop-in accepts that header only with a valid signature and then treats the request as coming from an address in the wanted country (taken from the GeoLite2 database), so WordPress renders exactly what a visitor from there would get. It sends at most two requests a second.<\/p><\/dd>\nWhere are cached pages stored?<\/h3><\/dt>\n
wp-content\/uploads\/wonderful-geo-page-cache\/<\/code>: the cached pages, the configuration the drop-in reads and the prewarm state, all as plain data files, never as code. An .htaccess<\/code> file closes the folder to web requests on Apache and LiteSpeed. On nginx, add a rule such as location ^~ \/wp-content\/uploads\/wonderful-geo-page-cache\/ { deny all; }<\/code>.<\/p><\/dd>\nDoes it work with another cache plugin?<\/h3><\/dt>\n
advanced-cache.php<\/code>; the plugin never overwrites another plugin's drop-in and tells you when one is installed.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.8<\/h4>\n\n
\n
1.0.7<\/h4>\n\n
\n
1.0.6<\/h4>\n\n
\n
1.0.5<\/h4>\n\n
\n
1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n
0.9.5<\/h4>\n\n
\n
0.9.4<\/h4>\n\n
\n
0.9.3<\/h4>\n\n
\n
0.9.2<\/h4>\n\n
\n
0.9.1<\/h4>\n\n
\n
0.9.0<\/h4>\n\n
\n