is this bug or its made to work like that
lets say we have object in cache name 00A5
url.com/some.js
vary=accept-encoding="gzip"
if some browser get the same object
url.com/some.js
vary=accept-encoding="deflate"
the md5 key wont match and it delete the old cached object with
accept-encoding="
On 28/08/2016 12:56 p.m., joe wrote:
> is this bug or its made to work like that
> lets say we have object in cache name 00A5
> url.com/some.js
> vary=accept-encoding="gzip"
>
> if some browser get the same object
> url.com/some.js
> vary=accept-encoding="deflate"
>
> the md5 key wont match
>If the above wasn't clear enough. This is how squid does it:
> key: MD5("http://url.com/some.js";)
>data: vary-marker object ("Vary:Accept-Encoding", ...)
>key: MD5("http://url.com/some.js"; + "accept-encoding=")
>data: no- Accept-Encoding variant response
>key: MD5("http://url.com/some
amos just by switching refresh from chrome to firefox and vice versa
2016/08/29 05:27:46 kid1| varyEvaluateMatch: Oops. Not a Vary match on
second attempt, 'http://www.annahar.com/'
'accept-encoding="gzip,%20deflate,%20sdch",
user-agent="Mozilla%2F5.0%20(Windows%20NT%205.1)%20AppleWebKit%2F537.36%2
