Thank you for your help. The perl script does work. I had:
external_acl_type propel_header_auth %{x-pun} /etc /squid/ident.pl x-pun
and the x-pun at the end of the external_acl_type was causing the problem. I wasn't sure why it was there but it caused the script to fail and took squid down with it. I also added quotes around the username (OK user="username") just in case (I was not sure the @ character was allowed). So far all things are working great!
Thanks again for all your help!
Ryan Lamberton
----- Original Message ----- From: "Henrik Nordstrom" <hno@xxxxxxxxxxxxxxx>
To: "Ryan Lamberton" <ryan@xxxxxxxxxxxx>
Cc: "Squid Users" <squid-users@xxxxxxxxxxxxxxx>
Sent: Wednesday, May 11, 2005 3:12 AM
Subject: Re: [squid-users] external_acl_type with http request header question
On Tue, 10 May 2005, Ryan Lamberton wrote:
As you can see I took another auth script and modified it. Even thought I get the same result as the sh script I tried to use this and it caused problems. Some of the base64 strings have the @familink.net in them as part of the username. Can Squid use that as a username?
Yes. Up to 64 characters is allowed.
What problems did you see in more detail?
Be warned of spaces,quotes and newlines. These requires special attention. The specification of the format you need to return to Squid is detailed in the description of the external_acl_type directive.
Just so you know, my only programming was in fortran!
Programming in procedural languages is mostly the same, just different syntax, so this is a benefit for you.
The perl language is very well documented, perhaps too well...
"man perlsyn" for detailed syntax description
"man perlop" for description of the available operators (compare/add/substract etc)
"man perltoc" for a table of contents of all the manuals included in the perl distribution if you need to look for something else.
there is also plenty of information on the web, and copy-pasting from other scripts doing similar things is also very helpful.
Regards Henrik