Previously we had spoken about implementing partial page caching (ESI) for Zero so we could remove X-CS variance for article content and use it only for partner banners. Is this still being pursued?
On Wed, May 8, 2013 at 10:24 PM, Yuri Astrakhan yastrakhan@wikimedia.orgwrote:
Hi, when we edit Zero configuration, it would be very beneficial to flush any cached pages in varnish that are related to the change.
For example, if I edit Beeline's banner settings, any objects with the header X-CS=250-99 should be purged, hopefully without any additional manual interaction. Without this purge, the cache will be stale for the next 30 days for the most common articles.
Now, according to the http://giantdorks.org/alain/exploring-methods-to-purge-varnish-cache/, varnish has an extensive matching support, and the author provides some PHP-based code to perform the cache flushing. What would we need to implement secure, automated partial varnish flushing in production?
Thanks! _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l