cache-control header in request dropped by varnish

[Dridi Boukelmoune]

Hi,

Letting a client enforce your cache policy is a bad idea IMHO, unless
you safeguard it to ensure only trusted clients can do that with an
ACL for instance.

You should probably upgrade to Varnish 4 first, Varnish 3 is no longer
supported.

Best Regards,
Dridi

On Fri, Sep 4, 2015 at 5:02 PM, Shiva <shiva2110 at gmail.com> wrote:
> Hi,
> We use varnish v3.0.4 , we are seeing this issue where clients are sending
> cache-control request header to varnish, but it is getting dropped before
> sending to backend app.
>
> I could see varnish receiving the header, also could see RxHeader having
> cache-control header from varnishlog. Our backend server is on tomcat, in
> tomcat access log the cache-control header is not seen.
>
> Is this an expected behavior ? RFC spec on cache-control header seem to
> mandate all caches to pass the header to the backend.
>
> Thanks!
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc