Hmm this may be useful "Users will be authenticated if squid is configured to use *proxy_auth* ACLs (see next question).
Browsers send the user's authentication credentials in the *Authorization*request header. If Squid gets a request and the *http_access* rule list gets to a * proxy_auth* ACL, Squid looks for the *Authorization* header. If the header is present, Squid decodes it and extracts a username and password. If the header is missing, Squid returns an HTTP reply with status 407 (Proxy Authentication Required). The user agent (browser) receives the 407 reply and then prompts the user to enter a name and password. The name and password are encoded, and sent in the *Authorization* header for subsequent requests to the proxy.............." http://wiki.squid-cache.org/SquidFaq/ProxyAuthentication Ronny On Fri, Nov 7, 2008 at 1:52 PM, Wire James <[EMAIL PROTECTED]>wrote: > Hi Guys > > I have this client that would like us to set up a squid cache that can; > 1. Proxy users' internet requests > 2. Cache sites > 3. Limit internet access based on user names and not IP address since DHCP > is the order of the day in their network. > 4. Selectively limit users from certain services e.g. prevent some from > accessing yahoo chat while allowing others. > > Any pointer to a manual that can help me easily setup the last two > requirements? Ideas on how best to implement it? > > Wire > > _______________________________________________ > LUG mailing list > [email protected] > http://kym.net/mailman/listinfo/lug > %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ > > The above comments and data are owned by whoever posted them (including > attachments if any). The List's Host is not responsible for them in any way. > --------------------------------------- > > >
_______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The List's Host is not responsible for them in any way. ---------------------------------------
