varnish caching with jsessionid being set
jlouis at peoplenetonline.com
Fri Mar 17 20:46:15 CET 2017
I must not be understanding your example on  as I'm still getting
The BereqHeader in varnishlog -b shows:
BereqHeader Cookie: JSESSIONID=4A1158EB11C9E93D6AD2A101BB9FA204;
and I'm seeing:
BerespHeader Cache-Control: no-cache, no-store, must-revalidate
BerespHeader Pragma: no-cache
Also, was there a part 2 to that blog?
On Thu, Mar 16, 2017 at 7:56 AM, Dridi Boukelmoune <dridi at varni.sh> wrote:
> On Wed, Mar 15, 2017 at 6:30 PM, Jim Louis <jlouis at peoplenetonline.com>
> > Hello,
> > I'm fairly new to varnish and have used it successfully in the past.
> Here they would like to use it but they have jsessionid tracking thru
> multiple VIPs. It seems that these jsessionids are being called cookies and
> I'm not able to cache anything.
> > Is there a way to use the jsessionids and accomplish the caching?
> Yes, there is. This is by far my "favorite" topic  so I wrote a
> blog post  about it. I would recommend carefulness and a solid
> understanding of HTTP and cookies first. It also depends a lot on
> whether your backend speaks proper HTTP and won't (mis)lead
> Varnish to do TheWrongThing(tm).
>  just in case it wasn't clear, it's not
>  https://info.varnish-software.com/blog/yet-another-post-on-
*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