Re: Selectively closing connections. Let's make a patch!

From: Muthukumar <kmuthu_gct@dont-contact.us>
Date: Thu, 1 Apr 2004 15:25:33 +0530

> mmmm..... Do you mean that i can close connections without new TAGs?
> If i write this in squid.conf:
> *****
> acl manager proto cache_objects
> acl bad_ip src 1.2.3.4
>
> http_access deny proto cache_objects bad_ip
> *****

I think i went for wrong option of manager acl.. forgot the manager acl for this requirement.
I have tested for this requirement.

Check this setting:

    acl test src client-ip-address/32

    Before http_access allow all give as
    http_access deny test

Test:

    Comment as
     #http_access deny test
     http_access allow all

Browse any url's

Test with
    http_access deny test
    http_access allow all

squid -k reconfigure
Now you will get denial message!! So you denied that access to that ACL

So the need for the close_connections TAG is not needed at this point.

> Will it close connections for bad_ip during reconfigure? Because even "http_access deny bad_ip" - do not close connections for
bad_ip!

For other acl's we have to block the GET method too..

acl ban1 dstdom_regex .google.com
acl get method GET
#http_access deny get ban1
http_access allow all

We can remove the access by
acl ban1 dstdom_regex .google.com
acl get method GET
http_access deny get ban1
http_access allow all
squid -k reconfigure

I hope your requirement is fully related to the acl setting ,methods and http_access setting at all.

Regards,
Muthukumar.
Received on Thu Apr 01 2004 - 02:55:34 MST

This archive was generated by hypermail pre-2.1.9 : Thu Apr 29 2004 - 12:00:03 MDT