On 20.04.20 15:29, James Adams wrote:
So I am new to squid and trying to take over from what was already in
place.
Do you have an example of what it should look like or a best practice
guide to use.
We can have up to 32 /24 blocks in our configurations.
I want to try and make the systems as ef
So I am new to squid and trying to take over from what was already in
place.
Do you have an example of what it should look like or a best practice
guide to use.
We can have up to 32 /24 blocks in our configurations.
I want to try and make the systems as efficient as possible knowing the
large
On 4/20/20 10:48 AM, James Adams wrote:
> acl 1 myportname 1 src all
I agree with Amos that you should consider automating these
configuration lines. Your access control and request routing
requirements are probably too special to warrant adding a new Squid feature.
While writing the config-gener
On 21/04/20 2:48 am, James Adams wrote:
> We have a few squid setups to handle large number of /24 IP blocks.
> I want to know is there an easier configuration to do this as we have to
> manually configure each conf file and can take a long time plus the fact
> of human error. I am trying to reduce
We have a few squid setups to handle large number of /24 IP blocks.
I want to know is there an easier configuration to do this as we have to
manually configure each conf file and can take a long time plus the fact
of human error. I am trying to reduce the number of lines needed and
make it a li
Dear all,
Sorry for missing the conf in my previous mail.
Below is my conf in squid 2.7
acl dest dst 10.68.8.146/32
http_access deny !dest
auth_param basic program ../libexec/ncsa_auth.exe ../etc/password.txt
acl User_Authorized proxy_auth REQUIRED
http_access allow User_Authorized
I tried to
