Re: Fetch called after pass

2008-05-22 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, "anda n andan" writes: >In our tests (varnish trunk rev 2635), vcl_fetch is still inserting >the request in cache even though it got a "pass" in vcl_recv. This is a case where the varnishlog output is a bit confusing: When you mark the request for pass in vcl_rec

Fetch called after pass

2008-05-22 Thread andan andan
Hi all. Whats happened with the possible bug related in http://projects.linpro.no/pipermail/varnish-misc/2007-July/000626.html: In our tests (varnish trunk rev 2635), vcl_fetch is still inserting the request in cache even though it got a "pass" in vcl_recv. Varnishlog attached. Thanks. Best re

Re: Fetch called after pass

2007-07-04 Thread Poul-Henning Kamp
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 has

Re: Fetch called after pass

2007-07-04 Thread André Cruz
Hello Poul. Thanks for the quick answer. On 2007/07/04, at 17:30, Poul-Henning Kamp wrote: The state diagram has morphed a bit lately, DES is busy updating the documentation and hopefully this will be covered RSN. In the meantime, here is a snapshot of the current -trunks stateenginge:

Re: Fetch called after pass

2007-07-04 Thread Poul-Henning Kamp
Hi Andre, The state diagram has morphed a bit lately, DES is busy updating the documentation and hopefully this will be covered RSN. In the meantime, here is a snapshot of the current -trunks stateenginge: http://phk.freebsd.dk/misc/_.pdf This is machine generated, see comment at the t

Fetch called after pass

2007-07-04 Thread André Cruz
Hello. After reading the vcl man page I was under the impression that after a "pass" return from vcl_recv the request was simply forwarded to the backend and the response would NOT be cached. In other words: pass - bypass cache and just forward response from backend. pipe - bypass cache and p