Aaron Pfeifer [EMAIL PROTECTED] writes:
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)
Aaron Pfeifer [EMAIL PROTECTED] writes:
(1) Upgrade to trunk (I was using 1.1.2)
May not be the best choice for all, I think
(2) Add set req.http.connection = close; immediately before the
pipe for a POST
Would this be an appropriate config snippet?
vcl_pipe {
set req.http.connection =
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,
