Hi. Sorry for not getting back sooner. The use case I have is have
backend determine when frequency reaches a threshold and set ttl
dynamically based on the rate. My goal is to tune cache using rates and
ttl values to ensure only most requested makes it into the cache as
opposed to adding 'bulk
On Sun, Jun 8, 2008 at 6:09 PM, Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> When processing ESI documents, Varnish will send "chunked" encoding
> and the number lines you see ("26", "19", "15" and "0") are the
> chunked headers, they say (in hex) how many characters follow.
Aha, I didn't know a
In message <[EMAIL PROTECTED]>, "Adria
no Nagel" writes:
>Hi,
>
>When using ESI (trunk r2652), varnish is adding extraneous characters
>to the output sent to the client, depending on the client being used.
>
>For example, for this html file:
>
>
>
>Teste ESI 8
>
>
>
>
>and this vcl snippet:
>
>
Hi,
When using ESI (trunk r2652), varnish is adding extraneous characters
to the output sent to the client, depending on the client being used.
For example, for this html file:
Teste ESI 8
and this vcl snippet:
} elseif (req.url ~ "^/t(este)?.html$") {
remove obj.http.Last-Mod
