varnish caching with jsessionid being set
jlouis at peoplenetonline.com
Mon Mar 20 16:34:33 CET 2017
On Mon, Mar 20, 2017 at 3:09 AM, Dridi Boukelmoune <dridi at varni.sh> wrote:
> On Fri, Mar 17, 2017 at 8:46 PM, Jim Louis <jlouis at peoplenetonline.com>
> > Dridi,
> > I must not be understanding your example on  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;
> > 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.
*Lead Systems Engineer*
4400 Baker Road, Minnetonka, MN 55343<br>
TOLL FREE 888-346-3486 x 622 | FAX 952-908-6129
PeopleNet is the leading provider of fleet mobility systems to the
transportation industry, including truckload, LTL, private, and energy
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the varnish-misc