When content on site is updated by WordPress, the plugin reaches out to the Varnish service with URL of the page, requesting the cache be deleted..
IP addresses of the website making the request may be recorded by the service, but there is no way to access them and use it to correspond with individuals or processes..
Use of this service is required for the cache checking order to provide up to date compatibility checks on plugins and themes that may conflict with running server based cache without needing to update the plugin every day...
If you have 3rd party proxy service you will need to add Varnish IP address on the Varnish -> Settings page..
The plugin does its best to add No Cache to javascript and CSS, however if theme or plugin doesn't use WordPress enqueues, then their content will be shown cached...
The problem arises when WordPress tries to send the purge request to your domain name and, with proxy, that means the proxy service and not your website..
On the other hand, if you told Varnish to listen on 0.0.0.0 you would need to check what IP you set your purge ACL to allow, and use that ..
DreamHost If you're using DreamPress and Cloudflare, go into Panel and click on DNS settings for the domain.
When flushing the whole cache, the plugin sends PURGE command of.* and sets X-Purge-Method header to regex...
This plugin is installed by default for all DreamPress installs on DreamHost, and I maintain it for DreamHost, but it was not originally DreamHost plugin.
Read more
Related items:
