On 21/06/2016 9:44 p.m., reinerotto wrote:
>> stay in sync
> naturally 90-something percent of the time. <
> I have a local dnsmasq running. squid and all clients synced to it.
> But the last 10% seem to cause the SECURITY ALERT.
>
>
> 2016/06/21 12:17:51.672 kid1| SECURITY ALERT: Host header fo
>stay in sync
naturally 90-something percent of the time. <
I have a local dnsmasq running. squid and all clients synced to it.
But the last 10% seem to cause the SECURITY ALERT.
2016/06/21 12:17:51.672 kid1| SECURITY ALERT: Host header forgery detected
on local=nn.nnn.nnn.nnn:443 remote=10.1.0.
On 21/06/2016 5:30 a.m., reinerotto wrote:
> I see quite a few messages like this one in my logs:
> squid[1327]: SECURITY ALERT: on URL: sa.scorecardresearch.com:443
> Running squid 3.5.19-20160524-r14057, https-intercept just for logging, so
> no bump.
> It is understood, that most likely this is
I see quite a few messages like this one in my logs:
squid[1327]: SECURITY ALERT: on URL: sa.scorecardresearch.com:443
Running squid 3.5.19-20160524-r14057, https-intercept just for logging, so
no bump.
It is understood, that most likely this is because of squids DNS and
browsers DNS not to be in
