On Mar 21, 2008, at 11:45 AM, Ricardo Newbery wrote:
>
> On Mar 21, 2008, at 5:08 AM, Dag-Erling Smørgrav wrote:
>
>> Ricardo Newbery <[EMAIL PROTECTED]> writes:
>>> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
I still don't understand why you want to go from hit to fetch.
Just
>>
On Mar 21, 2008, at 5:08 AM, Dag-Erling Smørgrav wrote:
> Ricardo Newbery <[EMAIL PROTECTED]> writes:
>> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
>>> I still don't understand why you want to go from hit to fetch. Just
>>> pass it.
>> Because a pass will not store the response in cache whe
Ricardo Newbery <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > I still don't understand why you want to go from hit to fetch. Just
> > pass it.
> Because a pass will not store the response in cache when it otherwise
> should if it contains a public token.
Dude
On Mar 20, 2008, at 6:07 AM, Dag-Erling Smørgrav wrote:
> Ricardo Newbery <[EMAIL PROTECTED]> writes:
>> If an authenticated request comes in and I have a valid cached copy,
>> Varnish should not return the cached copy *unless* the copy
>> contains a
>> public' token. It's not enough that Varn
Ricardo Newbery <[EMAIL PROTECTED]> writes:
> If an authenticated request comes in and I have a valid cached copy,
> Varnish should not return the cached copy *unless* the copy contains a
> public' token. It's not enough that Varnish previously tested for
> the public token before insertion as the
On Mar 20, 2008, at 4:34 AM, Dag-Erling Smørgrav wrote:
> Ricardo Newbery <[EMAIL PROTECTED]> writes:
>> I'm actually more interested in trying to reproduce the semantics of
>> the 'public' token. But I'm having trouble figuring out how to
>> implement this one in vcl. In the default vcl, authe
Ricardo Newbery <[EMAIL PROTECTED]> writes:
> I'm actually more interested in trying to reproduce the semantics of
> the 'public' token. But I'm having trouble figuring out how to
> implement this one in vcl. In the default vcl, authenticated requests
> are passed through before any cache check o
On Mar 20, 2008, at 2:15 AM, Dag-Erling Smørgrav wrote:
> Ricardo Newbery <[EMAIL PROTECTED]> writes:
>> [...]
>
> Yes, the spec is two years out of date.
Right. That much was apparent. My question again is shouldn't this
document be updated? And is there still an intent to implement any o
Ricardo Newbery <[EMAIL PROTECTED]> writes:
> [...]
Yes, the spec is two years out of date.
If you want Varnish to obey Cache-Control, it is trivial to implement in
VCL.
DES
--
Dag-Erling Smørgrav
Senior Software Developer
Linpro AS - www.linpro.no
__
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
10 matches
Mail list logo
