---Original Message-
>> From: squid-users <[hidden email]> On Behalf Of Amos Jeffries
>> Sent: Tuesday, May 15, 2018 21:28
>> To: [hidden email]
>> Subject: Re: [squid-users] SOLVED - SECURITY ALERT: Host header forgery
>> detected
>> The &q
>
> Eliezer Croitoru
> Linux System Administrator
> Mobile: +972-5-28704261
> Email: [hidden email]
>
>
>
> -Original Message-
> From: squid-users <[hidden email]> On Behalf Of Amos Jeffries
> Sent: Tuesday, May 15, 2018 21:28
> To: [h
-users@lists.squid-cache.org
Subject: Re: [squid-users] SOLVED - SECURITY ALERT: Host header forgery detected
On 16/05/18 02:02, Eliezer Croitoru wrote:
> Hey Martin,
>
> Technically there should be a way to inform Squid-Cache about multiple
> addresses for the same destination.
>
On 16/05/18 02:02, Eliezer Croitoru wrote:
> Hey Martin,
>
> Technically there should be a way to inform Squid-Cache about multiple
> addresses for the same destination.
> If Squid doesn't know that it's a real IP of the domains a partial solution
> is to use the same DNS service but it can
ect: Re: [squid-users] SOLVED - SECURITY ALERT: Host header forgery detected
> So I finally got the whitelist working, but now every other box on the
> "localnet", when trying to access the whitelist, gets a:
>
> 2018/05/14 07:40:18 kid1| SECURITY ALERT: on URL: www.ubuntu.c
> So I finally got the whitelist working, but now every other box on the
> "localnet", when trying to access the whitelist, gets a:
>
> 2018/05/14 07:40:18 kid1| SECURITY ALERT: on URL: www.ubuntu.com:443
> 2018/05/14 07:40:18 kid1| SECURITY ALERT: Host header forgery detected on
>
