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
Here is the response Amos gave, this is a known issue and apparently there
is no way to "ignore host header forgery issues" or bypass them in the
My understanding is that , maybe the short TTL is ok, but it is small
enough to where when a cloud based client is connecting to server a server
b to amazon S3 etc it can take a few seconds
Thus that 5 second TTL (which again is often 2-3 seconds) is small enough
Specifically some of these people (aws , google) in some dns situations
they are doing things that squid has been known to identify as host header
forgery just becuse it doesnt understand whats happening.
Also if im doing an S3 call pulling or pushing a big file which is very
common in cloud environments it can take 10-20 seconds for the request to
process , and if TTL expires mid stream , squid is for some reason flagging
as forgery and it hangs until it either returns to the same ip in
DNS by chance or until the connection is dropped.
Here is the note from Amos
>>* The cases where Squid still gets it wrong are where the popular CDN
*>>* service(s) in question are performing DNS actions indistinguishable to
*>>* those malware attacks. If Squid can't tell the difference between 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, <gar...@comnet.uz> wrote:
> On 2016-10-18 22:42, John Wright wrote:
>> Replying to the list
>> Yes i get that error on many different sites same exact error about
>> host headers.
>> Also if you watch the TTL on the amazonaws url i provided it changes
>> from 3 to 5 to 10 seconds to 60 to 10 back and forth.
>> If you go online to an dns lookup site like kloth i see via kloth 5
>> seconds TTL
>> i get a different TTL value at different times, it appears they dont
>> have a set TTL but they change it often and it varies.
>> Right now it appears to be a ttl of 60 seconds as you found but
>> earlier and over the weekend it has shown 5 seconds and even AWS
>> support verified it can vary as 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.
> The time interval between client's and Squid's name lookup is measured in
> milliseconds. So, in most cases, the would not be false positives in
> environments where same cashing DNS server is used.
> That specific issue you encounter except alert messages and Squid's
> inability to cache HTTP responses for "forged" HTTP requests?
> squid-users mailing list
Thank you for your time,
squid-users mailing list