Manuel Amador (Rudd-O) [EMAIL PROTECTED] writes:
In effect, the default Varnish policy of not caching Cookied requests
causes Varnish not to cache anything at all for most sites (you know,
there are tons of people out there using Google Analytics). Think about
it: why would people want the
Manuel Amador (Rudd-O) [EMAIL PROTECTED] writes:
Then another question (which will surely help me MUCH MORE than this
conundrum). I want to alter the Varnish caching policy to cache objects
whose response contains an ETag or a Last-Modified header, irrespective
of whether the user sent
Then another question (which will surely help me MUCH MORE than this
conundrum). I want to alter the Varnish caching policy to cache objects
whose response contains an ETag or a Last-Modified header, irrespective
of whether the user sent cookies along. That'll allow me to make
Varnish cache
I just signed up to the list so sorry if my questions have been asked a
million times already, if so i please point me to the responses.
This is what i want to do:
I want to setup anycasted proxys for static content that will have 48gig of
RAM, 6TB (6x1TB disks in a raid0 setup) of storage and
In message [EMAIL PROTECTED], Manuel Amador (Rudd-O) write
s:
I moved from Squid to Varnish and got stumped by your default policy.
Squid accelerated static objects by default, cookies or no cookies.
Varnish doesn't. Period.
It took me 15 minutes to install Squid, learn how to set it up as an
Manuel Amador (Rudd-O) [EMAIL PROTECTED] writes:
But my data seems to contradict your assumption that my assumptions are
flawed, since for each request on my Varnish log, there's a matching
request on my Apache log.
You assume that your site is typical of those that use Varnish. You
assume
See my last e-mail to find out the hack I had to implement in order for
Varnish to sort of work on my site.
I moved from Squid to Varnish and got stumped by your default policy.
Squid accelerated static objects by default, cookies or no cookies.
Varnish doesn't. Period.
It took me 15 minutes to
