[prev in list] [next in list] [prev in thread] [next in thread] 

List:       squid-dev
Subject:    Re: Caching responses with "Vary" responses
From:       Alex Rousskov <rousskov () measurement-factory ! com>
Date:       2012-07-24 14:35:08
Message-ID: 500EB29C.5000703 () measurement-factory ! com
[Download RAW message or body]

On 07/24/2012 02:09 AM, Henrik Nordström wrote:
> tis 2012-07-24 klockan 11:05 +1200 skrev Amos Jeffries:
> 
>> For the Vary meta its only a few hundred bytes normally as Alexander 
>> noted (~230 in his test).
>>
>> However some brilliant sites decide to use Cookie or User-Agent as one 
>> of the vary components. This can bloat the entry up to a worst-case of 
>> more than 64KB on some occasions. Other proxies and Apache allow ~10KB 
>> Cookie to be set so it is more the browser or scripted tools which 
>> generate these nasties.
> 
> That do not add to the Vary meta, but do add to the keying material.
> Vary meta should only be the HTTP header names listen in Vary or patched
> by Squid to work around broken servers.
> 
> Or is the shm cache using another keying method requiring the actual
> varying header data?

The shared memory cache does not have any key calculation code. It uses
the entry key supplied by Store.


HTH,

Alex.
[prev in list] [next in list] [prev in thread] [next in thread]