Thanks.
On Fri, Oct 18, 2019, 6:09 PM Alex Rousskov <
rouss...@measurement-factory.com> wrote:
> On 10/18/19 6:21 PM, Erick Perez - Quadrian Enterprises wrote:
> > acl allow_domains dstdomain "/etc/squid/allow_domains.txt"
>
> > Does squid reads the file at startup/reload and checks the ACL
> > i
On 10/18/19 6:21 PM, Erick Perez - Quadrian Enterprises wrote:
> acl allow_domains dstdomain "/etc/squid/allow_domains.txt"
> Does squid reads the file at startup/reload and checks the ACL
> in memory?
Yes.
> or is there a disk read for every time the ACL needs to be checked?
No.
Alex.
___
Hi,
I'm running squid with only allowed domains in
acl allow_domains dstdomain "/etc/squid/allow_domains.txt"
question: Does squid reads the file at startup/reload and checks the ACL in
memory?
or is there a disk read for every time the ACL needs to be checked?
If there's a disk read, will it bene
On 19/10/19 1:21 am, Vieri Di Paola wrote:
> On Fri, Oct 11, 2019 at 3:50 PM Amos Jeffries wrote:
>>
>> Note that this last entry is about a connection to port 443, whereas the
>> rest of the log is all about traffic to port 80.
>>>
>>> The Squid machine has no issues if I browse the web from comma
On 10/18/19 10:25 AM, Antonio SJ Musumeci wrote:
> I'd be happy to post this on squid-dev / submit a pull request.
Please do, assuming you are willing to do the legwork necessary to go
from a proof of concept (that has already changed several times during
this short discussion!) to the final offi
On 10/18/19 10:17 AM, Robert Senger wrote:
> there's a group of clients that should be configured to load
> websites via ipv4 only.
> The only way I found so far is to set an invalid ipv6 outgoing address:
>
> tcp_outgoing_address fd20::1 proxy-extra
> tcp_outgoing_address 172.16.4.244 prox
On 10/18/2019 9:49 AM, Alex Rousskov wrote:
Actually, the location of shared memory segments is chosen by the OS.
Not all OSes do what Linux does. The code dealing with [naming] shared
memory segments is more complicated than you probably imagine. However,
let's not spend time arguing about these
Hi there,
I am running squid on a dual stacked host. Both ipv4 and ipv6
connectivity is fully functional.
Now there's a group of clients that should be configured to load
websites via ipv4 only.
acl proxy-extra localip fd10:96e4:b552::43
acl proxy-extra localip 172.16.4.243
I know there's a
On 10/17/19 7:13 PM, Antonio SJ Musumeci wrote:
> On 10/17/2019 5:47 PM, Alex Rousskov wrote:
>> Unfortunately, a simple implementation may produce a lot of false
>> warnings in some environments while a quality implementation may not be
>> as easy as you think: Accessing free space info may requir
On Fri, Oct 11, 2019 at 3:50 PM Amos Jeffries wrote:
>
> Note that this last entry is about a connection to port 443, whereas the
> rest of the log is all about traffic to port 80.
> >
> > The Squid machine has no issues if I browse the web from command line,
> > eg. 'links http://www.linuxheadqua
10 matches
Mail list logo
