As an early christmas gift, here is a snapshot of the web GUI being
developed for the 2.1 release:
http://varnish.projects.linpro.no/wiki/WebGui
It is not 100% finished (saving state and security being the major
issues and the code needs some cleaning), but I hope people can test and
play
Hi All,
In testing varnish in different situations, I came accross a backend that
sends no caching information in its responses, no Expires, cache-control or
anything.
Ok, I thought, I'll just set the TTL on that object (namely an html page) in
VCL.
Well, turns out varnish may be setting the ttl
Hi!
Is there a place where I can alter the backend response before it is
inserted into the cache?
Thanks!
Alecs
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc
Alecs Henry alecshe...@gmail.com writes:
What about cookies? Can varnish log cookie values? Or does it fit in
the same problem as the first message?
Varnish can and does log cookies. See the varnishlog(1) man page.
DES
--
Dag-Erling Smørgrav - d...@des.no
Hi,
Alecs Henry wrote:
Well, turns out varnish may be setting the ttl all right (I do it in
vcl_fetch, but frankly there really is no way to see if it is set
correctly or not! or is there?) but the page always gets a PASS, never a
HIT. Age: is set to 0 by varnish.
The client probably sends
Thanks Dag, I must have missed it!
Alecs
On Fri, Dec 12, 2008 at 7:08 PM, Dag-Erling Smørgrav d...@des.no wrote:
Alecs Henry alecshe...@gmail.com writes:
What about cookies? Can varnish log cookie values? Or does it fit in
the same problem as the first message?
Varnish can and does log
Hi Per,
I'm looking into changing the headers all right! Where do I do that in VCL?
I wanted to try to set some cache control headers before the object was put
into varnish cache.
Does that even make sense?
Thanks!
Alecs
On Fri, Dec 12, 2008 at 7:20 PM, Per Buer pe...@linpro.no wrote:
Alecs
Hi Per,
I'm actually using the cookies in the cache (using the information provided
on the website -- set req.hash += req.http.cookie;) and it works just fine!
One thing that the backend does is vary on user-agent, not only
content-encoding (I've removed the UA vary on the response, though).
So