In case anyone runs into the same problem, with the help from the folks on
#varnish, the problem is that piping a POST will cause the cache to be
bypassed if the session remains open. The solution is to either:
(1) Upgrade to trunk (I was using 1.1.2)
(2) Add "set req.http.connection = "close";"
Is there a possible reason Varnish would not immediately cache a file when
put in front of s3, requiring multiple subsequent hits before caching? The
scenario is:
The file "foo.png" is uploaded to the web server and then stored onto S3.
When a request is made for http://localhost/files/foo.png, V
Hi,
Im experiencing a strange problem when using varnish in front of apache2.
I m running a php website where I log the client IP to the usertable in
the database.
I first check the Client IP to see if it is a valid IP, if not, I check
the "x-forward-for" for a valid ip (I check for multiple IP
Hi,
We have a setup with varnish in front of a lighttpd+fastcgi combo. For some
reason or other the application doesn't send any cache control headers. Instead
of doing the sensible thing (prodding the developers to fix it in the backend)
I have taken it upon myself to fix it via VCL.
However
