Re: Re: Caching responses with "Vary" responses

OK. So, regarding the log I've previously attached, those 235 bytes
(vary header) shall be saved on C447BB767EC4BC4DAC1820CE7999F4C4, while
the response itself (7808 bytes) can be saved on any other, right?

If it's right, we got two problems here:
1) Vary header hash is not correct (shall be
C447BB767EC4BC4DAC1820CE7999F4C4, but got
4DB6DCFE80050CF0CA306DB8EDFF718E)
2) Vary header doesn't get saved to the store
( StoreEntry::checkCachable: NO: private key)

On Thu, 2012-07-12 at 22:29 +0200, Henrik Nordström wrote:
> tor 2012-07-12 klockan 14:32 +0400 skrev Alexander Komyagin:
>
> > 2) What are those 235 bytes that are written to the 'vary' storeEntry
> > (created in setPublicKey)? And what is the purpose of that additional
> > storeEntry?
>
> It's the Vary header of the response so future lookups know how to build
> the store key.
>
> This object should get saved on the same store hash as an response for
> the same URL without Vary.
>
> Regards
> Henrik
>

-- 
Best wishes,
Alexander Komyagin