On 7/13/19 7:37 AM, Amos Jeffries wrote:
> On 13/07/19 9:55 pm, --Ahmad-- wrote:
>> i want it when squid access / contact with 1.2.3.4
> Use "dst" ACL for destination IP's.
> However, requests are generated before sending. Squid does not know
> which IP will *in future* be used to deliver the req
On 13/07/19 9:55 pm, --Ahmad-- wrote:
>
>
> i want it when squid access / contact with 1.2.3.4
>
>
Use "dst" ACL for destination IP's.
However, requests are generated before sending. Squid does not know
which IP will *in future* be used to deliver the request. So this is
unlikely to work prop
i want it when squid access / contact with 1.2.3.4
Thanks
> On 13 Jul 2019, at 12:36, Matus UHLAR - fantomas wrote:
>
> when accessing 1.2.3.4 or whn your client is 1.2.3.4?
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://
On 13.07.19 12:20, --Ahmad-- wrote:
say i have a set of rules to block some certain types of headers as below :
header_access Pragma deny all
header_access Keep-Alive deny all
but i want those above two headers allowed when accessing ip 1.2.3.4
is my config below is correct ? i tested but di
hello folks .
say i have a set of rules to block some certain types of headers as below :
header_access Pragma deny all
header_access Keep-Alive deny all
but i want those above two headers allowed when accessing ip 1.2.3.4
is my config below is correct ? i tested but didn’t work
acl allowip
