POST requests to ESIs

Caunter, Stefan scaunter at topscms.com
Wed Jan 12 22:51:02 CET 2011


From: jsansbury at lullabot.com [mailto:jsansbury at lullabot.com] On Behalf
Of James Sansbury
Sent: January-12-11 4:50 PM
To: Caunter, Stefan; varnish-misc at varnish-cache.org
Subject: Re: POST requests to ESIs

 

On Wed, Jan 12, 2011 at 4:03 PM, Caunter, Stefan <scaunter at topscms.com>
wrote:

On Wed, Jan 12, 2011 at 1:39 PM, Caunter, Stefan <scaunter at topscms.com>
wrote:

Even on heavily commented sites, the number of POSTs for new comments
will be low per second. Issue always seems to be pulling comments for
each page load. Loading comments with a GET, with a ttl > 0 seems to
work well for us (no ESI). Is there a reason you are running with TTL at
zero?

 

Yeah, sorry, it was not so much about the TTL as the ability to still
lookup the cached page and pass the POST through to the ESI. I
understand we can increase the TTL of the ESI, but the real goal here is
to have a separate ESI only server that handles all authenticated
traffic, while keeping the frontend server served completely from the
Varnish cache.

 

Ah yes. Consider a subdomain. We pipe for cases like this.

 

Can you describe a bit more what you mean? We have our frontend site,
origin.example.com, which has ESIs pointing to ugc.example.com (ugc ==
user generated content). If you pipe in vcl_recv, ESIs are not
processed. Maybe I'm missing something. :)

 

Indeed, I'm not using ESI, but if I need varnish to handle something I
pass.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20110112/f4511c5a/attachment-0003.html>


More information about the varnish-misc mailing list