Comments on: No ESI processing, first char not ‘ http://cd34.com/blog/infrastructure/no-esi-processing-first-char-not/ This is my blog, there are many others like it but this one is mine. Wed, 21 Jul 2010 11:24:11 +0000 hourly 1 http://wordpress.org/?v=3.0 By: <img src='http://cd34.com/blog/wp-content/plugins/rpx/images/facebook.png'/> cd34 http://cd34.com/blog/infrastructure/no-esi-processing-first-char-not/comment-page-1/#comment-757 cd34 Fri, 04 Dec 2009 07:41:37 +0000 http://cd34.com/blog/?p=837#comment-757 Rather than disable mod_deflate on the backend, for ESI parsed pages you can use VCL to strip out the Accept-Encoding and Vary headers. In vcl_recv, within a condition that matches the urls/hostname you can place: <pre> unset req.http.Accept-Encoding; unset req.http.Vary; </pre> and within vcl_fetch, create a condition that matches the uri's that you want to parse for ESI and place: <pre> esi; </pre> This will allow the backend to serve content with mod_deflate/mod_gzip while allowing ESI to be procesed. Rather than disable mod_deflate on the backend, for ESI parsed pages you can use VCL to strip out the Accept-Encoding and Vary headers. In vcl_recv, within a condition that matches the urls/hostname you can place:

   unset req.http.Accept-Encoding;
   unset req.http.Vary;

and within vcl_fetch, create a condition that matches the uri’s that you want to parse for ESI and place:

       esi;

This will allow the backend to serve content with mod_deflate/mod_gzip while allowing ESI to be procesed.

]]>