The zero ESI change is now live, but is enabled only when X-FORCE-ESI
header is set to 1. Also, it won't work until varnish enables ESI
support for zero requests (see
dochttps://www.varnish-cache.org/docs/3.0/tutorial/esi.html
)
I propose the following deployment steps:
1) set beresp.do_esi =
Hi Yuri,
On Jun 14, 2013, at 7:16 PM, Yuri Astrakhan yastrak...@wikimedia.org wrote:
Based on many ideas that were put forth, I would like to seek comments on
this ZERO design. This HTML will be rendered for both M and ZERO subdomains
if varnish detects that request is coming from a zero
Hi Mark,
On Tue, Jun 18, 2013 at 11:58 AM, Mark Bergsma m...@wikimedia.org wrote:
* All non-local links always point to a redirector. On javascript capable
devices, it will load carrier configuration and replace the link with
local
confirmation dialog box or direct link. Without
Based on many ideas that were put forth, I would like to seek comments on
this ZERO design. This HTML will be rendered for both M and ZERO subdomains
if varnish detects that request is coming from a zero partner. M and ZERO
will be identical except for the images - ZERO substitutes images with
I think we'll want to make those 302s given that UAs may make the redirects
permanent without consideration for Vary: headers, some of which the UA
won't actually know. Will add that to the RFC shortly.
On Fri, Jun 14, 2013 at 10:16 AM, Yuri Astrakhan
yastrak...@wikimedia.orgwrote:
Based on
