Re: [squid-users] Host header forgery policy in service provider environment

2016-01-06 Thread Amos Jeffries
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

Re: [squid-users] Host header forgery policy in service provider environment

2016-01-06 Thread Garri Djavadyan
>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

Re: [squid-users] Host header forgery policy in service provider environment

2016-01-01 Thread garryd
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

Re: [squid-users] Host header forgery policy in service provider environment

2015-12-31 Thread Amos Jeffries
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

[squid-users] Host header forgery policy in service provider environment

2015-12-30 Thread Garri Djavadyan
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