On 6/01/2016 10:10 p.m., Garri Djavadyan wrote:
>> On 2015-12-31 00:01, Garri Djavadyan wrote:
>>> Hello Squid members and developers!
>>>
>>> First of all, I wish you a Happy New Year 2016!
>>>
>>> The current Host header forgery policy effectively prevents a cache
>>> poisoning. But also, I notic
>On 2015-12-31 00:01, Garri Djavadyan wrote:
>> Hello Squid members and developers!
>>
>> First of all, I wish you a Happy New Year 2016!
>>
>> The current Host header forgery policy effectively prevents a cache
>> poisoning. But also, I noticed, it deletes verified earlier cached
>> object. Is i
On 2015-12-31 13:31, Amos Jeffries wrote:
On 2015-12-31 00:01, Garri Djavadyan wrote:
Hello Squid members and developers!
First of all, I wish you a Happy New Year 2016!
The current Host header forgery policy effectively prevents a cache
poisoning. But also, I noticed, it deletes verified earl
On 2015-12-31 00:01, Garri Djavadyan wrote:
Hello Squid members and developers!
First of all, I wish you a Happy New Year 2016!
The current Host header forgery policy effectively prevents a cache
poisoning. But also, I noticed, it deletes verified earlier cached
object. Is it possible to implem
Hello Squid members and developers!
First of all, I wish you a Happy New Year 2016!
The current Host header forgery policy effectively prevents a cache
poisoning. But also, I noticed, it deletes verified earlier cached
object. Is it possible to implement more careful algorithm as an
option? For e
