On Fri, Mar 17, 2017 at 8:46 PM, Jim Louis <jlo...@peoplenetonline.com> wrote: > > Dridi, > > I must not be understanding your example on [2] as I'm still getting > everything passed.
Hi Jim, Thanks for letting me know, I will try to clarify this part. > The BereqHeader in varnishlog -b shows: > BereqHeader Cookie: JSESSIONID=4A1158EB11C9E93D6AD2A101BB9FA204; > pfmhelp=1; _ga=GA1.2.1694534677.1489779146; > TrackJS=f2465051-cb66-4cfa-8a47-5c7a5d07aab4; navigation=520533110%7C4130 > > and I'm seeing: > BerespHeader Cache-Control: no-cache, no-store, must-revalidate > BerespHeader Pragma: no-cache The backend is telling Varnish, and ultimately the client, that the response cannot be cached. Depending on your version of Varnish it will indeed result in subsequent passed transaction. > Also, was there a part 2 to that blog? Part 2 is written, but still an early draft so not published yet. Cheers, Dridi _______________________________________________ varnish-misc mailing list varnish-misc@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc