Safety of setting "beresp.do_gzip" in vcl_backend_response

[Guillaume Quintard]

You are right, subsequent requests will just be passed to the backend, so
no gzip manipulation/processing will occur.

-- 
Guillaume Quintard

On Thu, Apr 13, 2017 at 12:49 AM, Nigel Peck <np.lists at sharphosting.uk>
wrote:

>
> Hi,
>
> I am implementing compression in vcl_backend_response, by setting
> "beresp.do_gzip" on appropriate Content-Type's. I am wondering if it is
> safe to do this even on responses that may subsequently get set as
> uncacheable by later code?
>
> It seems safe to me, but just wanting to check in case I'm missing
> something. I assume that if a response is subsequently set uncacheable then
> "beresp.do_gzip" will simply have no affect?
>
> Thanks
> Nigel
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20170413/5e1c433b/attachment.html>