I need to build a hierachical caching plattform. The Goal is, to have
multiple frontends that will expire in sync.
Currently we cascade a pool of Cacher in front of a single Intermediate
Cache. The Front-Cacher will honor any Age-Header it will retrieve
from the Intermediate.
So cacher-1 will
On lun, 2007-07-02 at 22:42 -0700, Ask Bjørn Hansen wrote:
On Jul 2, 2007, at 7:26, Manuel Amador (Rudd-O) wrote:
I never insulted any of you.
You really should go see a therapist. Just tell him or her: People
think I'm a rude idiot - please help me.
I will convey your thoughts to my
Thanks a lot. Will use this to tune Varnish better. This functionality
is not mentioned in the manual page of vcl, nor was it conveyed to me by
Dag-Erling or Poul-Henning.
On mié, 2007-07-04 at 09:37 +0530, Anup Shukla wrote:
Manuel Amador (Rudd-O) wrote:
The optimum behaviour would be
On Jul 4, 2007, at 12:23 AM, Christoph wrote:
I need to build a hierachical caching plattform. The Goal is, to have
multiple frontends that will expire in sync.
[...]
Is this possible with varnish?
I haven't tried it with varnish, but I think it should work if you
use Expires: ... rather
Helo,
varnish was stopped with this error:
0 CLIRd ping
0 CLIWr 0 200 PONG 1183565922
0 Debug Create worker thread failed 12 Cannot allocate memory
0 CLIRd ping
0 CLIWr 0 200 PONG 1183565925
0 Debug Create
In message [EMAIL PROTECTED], =?ISO-8859-1?Q?And
r=E9_Cruz?= writes:
From what I can see, if vcl_recv() returns pass the request can
still be cached by logic in vcl_fetch(), right?
No, this is one of the things that figure does not show: the object
created by vcl_pass() is not in the hash
