Conditionally Disabling GZIP in Order to Serve ESI

Follow
Andri Antoniades

[Edit: ESI + GZIP can now be supported in certain circumstances. Please contact support@fastly.com to discuss turning this on. Note: You will require a paid account and a TLS product with us in order to do this].

Fastly’s version of Varnish currently doesn’t support the use of ESI with GZIP. But you can conditionally disable GZIP in order to serve ESI when it’s appropriate for your service.

Assuming you’ve already had custom vcl enabled, you’ll then want to insert some ESI logic into the Fastly boilerplate under vcl_fetch.

In this example, we’ll enable ESI based on Content-Type:

sub vcl_fetch {
#FASTLY fetch
  if ( beresp.http.Content-Type ~ "^text/html" ) {
    esi;
  }

Next, you’ll want to add unset bereq.http.accept-encoding to vcl_miss:

sub vcl_miss {
unset bereq.http.accept-encoding;
#FASTLY miss
  return(fetch);
}

Finally, you’ll create a GZIP object in the UI and—based on our example above—remove text/html from the content types to be compressed and the html extension, if it’s there.

These steps should ensure that when you’re not serving ESI, you’re still compressing, but when you are serving ESI, your content remains uncompressed, allowing your ESI content to render consistently.

0

Comments

9 comments

Sort by Date Votes
  • Frank Farmer

    There's a missing semicolon after unset bereq.http.accept-encoding

    0
    Comment actions Permalink
  • Justin

    Thanks @Frank_Farmer

    0
    Comment actions Permalink
  • Ilya Kaplan

    Hi Justin,

    I ping with this question every now and then. Is there any plan to fix ESI with GZip limitation? After all Varnish 3 does support it.

    Now question related to workaround mentioned here. Turning gzip off for all HTML would drastically increase content size. Wouldn't it seriously impact on performance of site that uses this workaround?

    0
    Comment actions Permalink
  • Justin

    You're in luck! We're almost ready to announce support but not quite yet... If you'd like to test it out in the meantime send in a Support ticket and we can let you the current state.

    0
    Comment actions Permalink
  • Justin

    Don't jinx it! :sweat_smile: Seriously though, the release date hasn't been given, but it's being tested by customers now, so it won't be too long...

    0
    Comment actions Permalink
  • markwainwright

    Hi @justin. Just wondering if there's any update on when ESI + gzip will be supported?

    0
    Comment actions Permalink
  • Justin

    Hi @markwainwright. Enabling will require emailing support@fastly.com. It's fairly quick and easy to do now.

    0
    Comment actions Permalink
  • Chaim Klar

    we had some instances where ESI was not executing (no interpolation took place) 

    we added to VCL_FETCH

    unset req.http.accept-encoding;

    in addition to having in VCL_MISS

    unset bereq.http.accept-encoding;

    and it helped.

    do I make any sense? maybe it's because we have shielding?

    0
    Comment actions Permalink
  • Justin

    Hi Chaim Klar

    If you're not seeing ESI executing where you believe it should, it's likely to be because the content is coming in as compressed.

    I'm glad you found a solution but if you need anything else, do send it in as a ticket via the Support portal or an email to support@fastly.com so we can investigate.

    0
    Comment actions Permalink

Please sign in to leave a comment.

New post