[squid-users] Development of SQL-based ACL?

[Didde Brockman <didde_brockman@xxxxxxx>]

Hello users,

I'm investigating the possibilities of using Squid in a large  
corporate environment. We have found the documentation to be rather  
complete, and after a period of evalutation two questions has come up  
and now I'm hoping you guys are able to help me out.

1. Are there any references available on _large_ projects  
incorporating Squid? "Large" being defined as roughly 100,000 -  
200,000 clients 24/7. The numbers available on the site are outdated  
and seems to be focused on smaller solutions. I'm looking for some  
example hardware setups or basic numbers pertaining to the load of  
systems experiencing _heavy_ traffic.

2. We would like to be able to administer ACL's through rules stored  
in a external database (SQL). Also, this would pair an IP with  
specific settings for a specific client, i.e. 10.0.0.122 is allowed  
to do this, but not that. Also, if client 10.0.0.122 requests a  
"forbidden" HTTP-resource its request should be redirected to a local  
page. Basically, these settings should be customisable for all users  
so they can acknowledge a forbidden resource, absorb the information  
on the local page (the target of the redirect) and then choose to  
continue on to their (forbidden) destination or not.

For the second point, I'm assuming this would require us to contract  
a developer to make the necessary alterations the Squid's source  
code, so I'm also curious as to your experiences (if any) with known  
companies offering to do customisations on Squid.

I would really appreciate any input on this as it sure would help out  
a lot. Sorry about all the typos and poor language, but my english is  
a bit rusty.



Kind Regards,
Didde