Re: [squid-users] external_acl_type with http request header question

[Ryan Lamberton]

hmm... is there an example of a "silly helper" out there I can use/modify? 
And will the Ident acl "set" the username the same way the proxy_auth does 
so my filtering program can identify the username?  Why should I disable 
client side persistent connections?

Thank you very much for the help.
Ryan Lamberton
----- Original Message ----- 
From: "Henrik Nordstrom" <[EMAIL PROTECTED]>
To: "Ryan Lamberton" <[EMAIL PROTECTED]>
Cc: <squid-users@squid-cache.org>
Sent: Friday, May 06, 2005 2:15 PM
Subject: Re: [squid-users] external_acl_type with http request header 
question


On Thu, 5 May 2005, Ryan Lamberton wrote:
I have a question on external_acl_type -- I think.  I have Squid 2.5 
stable 3 setup and use propel accelerator to pass the header HTTP_X_PUN 
with the username that authenticated in propel.  What I want to have 
happen is that username passed from Propel to be used by squid for 
proxy_auth.
Ok. As you suspect this can (almost) be done with external_acl_type.
What you need is
a) A silly helper echoing the username back to Squid. This helper will be 
given the username from the header as input by Squid.

b) You need to use the ident acl, not proxy_auth. And should also disable 
client side persistent connections when doing this (the 2.5 implementation 
piggy backs on the ident user name which is connection oriented...)

Regards
Henrik