o i keep using squid?
On Tue, Oct 18, 2016 at 2:10 PM, John Wright wrote:
> In response to it not being a false positive , maybe its not specifically
> the TTL but in this other article on the mailing lists someone else had the
> same issue
>
>
> Here is the response Amos gave,
een an
*>>* attack and normal DNS behaviour the only code change possible is to
*>>* disable the check (see above about the risk level).
*>>
On Tue, Oct 18, 2016 at 2:01 PM, wrote:
> On 2016-10-18 22:42, John Wright wrote:
>
>> Hi
>>
>> Replying to the lis
low as 5 seconds.
That being said , when it is changing every 3-5 seconds which comes and
goes , squid gives the header forgery errors as shown before.
On Tue, Oct 18, 2016 at 12:30 PM, wrote:
> On 2016-10-18 18:32, John Wright wrote:
>
>> Hi,
>>
>> I have a constant
Hi,
I have a constant problem with Host header forgery detection on squid doing
peek and splice.
I see this most commonly with CDN, Amazon and microsoft due to the fact
there TTL is only 5 seconds on certain dns entries im connecting to. So
when my client connects through my squid i get host hea
