"Poul-Henning Kamp" <[EMAIL PROTECTED]> writes:
> "Michael S. Fischer" <[EMAIL PROTECTED]> writes:
> > So does Varnish close HTTP Keep-Alive backend connections after an
> > idle period? or not?
> We _never_ close a backend connection until the backend closed its
> end.
OK, my mistake. I thought
In message <[EMAIL PROTECTED]>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=
writes:
>While we're all gathered around the wishing well, I wish "remove" was
>named "unset" (see attached patch) and "unset" on a run-time parameter
>should reset it to its default value.
I decide that "remove" was a better w
"Poul-Henning Kamp" <[EMAIL PROTECTED]> writes:
> "Dag-Erling Smørgrav" <[EMAIL PROTECTED]> writes:
> > While we're all gathered around the wishing well, I wish "remove"
> > was named "unset" (see attached patch) and "unset" on a run-time
> > parameter should reset it to its default value.
> I deci
Am Mittwoch 19 März 2008 12:31:04 schrieb Dag-Erling Smørgrav:
> > and, sorry if this is FAQ, are the storage files persistent, that
> > is, will they survive a restart of varnish or reboot of the
> > machine, or do you always start with an empty cache?
>
> Varnish always startes with an empty cach
From previous discussions on this list, I've been operating on the
understanding that Varnish ignores all Cache-Control tokens in the
response except for max-age and s-maxage. But the following snippet
from the varnish specification document seems to suggest otherwise.
Does this documen
I'm looking at the default vcl and I see the following stanza:
sub vcl_hit {
if (!obj.cacheable) {
pass;
}
deliver;
According to the vcl man page:
obj.cacheable
True if the request resulted in a cacheable re
