According to HTTP/1.1 specification, the precedence is not determined by
the keyword, but by the value: The shorter age is to be taken.
Regards
Markus
> -Original Message-
> From: Chris Woodfield [mailto:[EMAIL PROTECTED]
> Sent: Freitag, 26. September 2008 23:46
> To: Squid Users
> Subje
f
> Of Adrian Chadd
> Sent: Donnerstag, 4. September 2008 02:27
> To: Markus Karg
> Cc: Amos Jeffries; squid-users@squid-cache.org
> Subject: Re: [squid-users] min-fresh / max-stale not working?
>
> When someone contributes the work or funds development.
>
>
>
> A
ber 2008 15:40
> To: Markus Karg
> Cc: squid-users@squid-cache.org
> Subject: Re: [squid-users] min-fresh / max-stale not working?
>
> Markus Karg wrote:
> > Sorry it was a typo. The test was done mit SQUID-2.7-STABLE4
> actually.
> > The HTTP/1.1-Support is only ex
Sorry it was a typo. The test was done mit SQUID-2.7-STABLE4 actually.
The HTTP/1.1-Support is only experimental???
> -Original Message-
> From: Amos Jeffries [mailto:[EMAIL PROTECTED]
> Sent: Mittwoch, 3. September 2008 07:14
> To: Markus Karg
> Cc: squid-users@squid-cach
Dear SQUID Community,
it seems as if SQUID is not dealing correctly with "min-fresh" and
"max-stale":
Currently we are evaluating the use of SQUID-2.6-STABLE4. It all seems
to work pretty well, but just "min-fresh" and "max-stale" is not
working. Our client agent wants to guarantee to get data th
