Varnish will not (by default) cache pages with set Cookies. Cookies introduce state to HTTP and thus Varnish can't know whether or not the page has changed.
Varnish will not (by default) cache pages with set Cookies. Cookies introduce state to HTTP and thus Varnish can't know whether or not the page has changed. Your above code snippet though will not fix your issue.It will just remove Cookie headers altogether.
(I.e. You PHP backend will not receive session cookies.) Depending on how exactly your site looks like, you would either want to: Leave behavior as is: If you for example have some place on the page saying the username of the logged in user you don't want that to be cached. Basically in this case Varnish will only cache contents for guest (i.e.
Users without sessions) If you don't have such a user-dependent box on every page you can cache everything apart from the user-dependent (e.g. Shopping cart) pages.
Great, thanks NikiC; At the moment we do have session-dependent features on every page, so we'll have to have a tinker with the workings of the site I think! Thanks again – barryfudge Oct 14 '11 at 11:29 In complement to this answer I would say that if you want a more detailled cache handling, not based on pages but on pieces of final user pages you should look at Varnish ESI capabilities. – regilero Oct 14 '11 at 12:13.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.