No WordPress configuration needed.
Well. That’s true. For 99.9999% of sites, there isn’t any config needed.
The define you noted is only needed if you’re putting another proxy in front of Varnish (like CloudFlare). Which … well I don’t know why people put proxies in front of proxies, but hey.
You shouldn’t need to put in 127.0.0.1 in the define, though, at all, and it makes me think you may have Varnish configured oddly, since if you’re using that redirect, then you can’t do this on your server either:
curl -X PURGE "http://www.example.com/"
See that’s all the plugin’s really doing. It’s automating that call. So if your site is setup that you can’t run a purge call direct to your domain, then yeah, that would be a problem. And a weird setup, in my experience.
Thread Starter
Zeokat
(@zeokat)
My site not allow external PURGE requests from the domain itself or public IP. From my point of view allow that is a very very bad practice and you can fall into security issues.
If you allow external PURGE requests, an attacker can clear all the cache or who knows what can happens tomorrow if someone discover a vulnerability with malformed PURGE requests… i´m paranoic perhaps but in security all paranoia is an extra 😛
I´m not using any proxy, i simply restricted the PURGE requests to 127.0.0.1 or localhost.
And i continue thinking the same, most of sites not will work without editing wp-confip.php, Why? it´s very simple… check default config of Ubuntu, Debian or CentOS Varnish installations, check Varnish documentation, etc… All VCL codes an examples never allow external PURGE requests by default.
I think you did something odd, since I know we block external purge calls too and we don’t need to define that IP address at all. You’re the only person I’ve heard of having this issue.
The purge isn’t coming ‘externally’ – it’s coming via localhost. The only reason you have to define that ip is whenit can’t (like you have a proxy and your IP doesn’t match the domain… Which I have no idea why you’re claiming your site doesn’t. I use this on Ubuntu and Debian and have no issues.
I run a VPS using CentOS and this plugin runs perfectly with no WP config required.
