Hi Frederick - first, thank you for the wonderful caching plugin. Very well done.
I recently ran into an issue with PgCache that I was hoping you could help me with. Here's the setup:
- varnish running on port 8080
- apache running on port 80
Requests to http://localhost:8080 hit varnish and varnish then requests pages from WP using http://localhost (no port #). What I have noticed is that the request from Varnish causes PgCache to generate files with this path:
/wp-content/cache/page_enhanced/localhost/_index.html
But when I update a post from /wp-admin in WP, it uses this path to try to figure out where to invalidate the PgCache files:
/wp-content/cache/page_enhanced/localhost:8080/_index.html
Since the two don't match, article updates don't invalidate the static html file and the client shows the same content as before the edit.
For now I just used a symlink so that both paths lead to the same files and that works... but someone else must have run into this situation before so I'm wondering if there is a more elegant and sustainable solution?
Thanks!