ESI for older browsers, and JavaScript otherwise are still on the table,
but that's orthogonal to the varnish cache purge -- if we use ESI, the
banner will be cached and will need to be purged. If we use JavaScript, the
JSON configuration blob will need to be purged. The only difference is the
actual "purging expression".
On Thu, May 9, 2013 at 2:14 PM, Arthur Richards <arichards(a)wikimedia.org>wrote;wrote:
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(a)wikimedia.org
wrote:
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(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l