Squid-2.5 URL encodes the login and password to be able to deal with
complex passwords. Beacuse of this any auth helpers used with Squid-2.5
or later should be designed for use with Squid-2.5 and later (needs to
URL-decode the login and password fields).
http://www.squid-cache.org/Versions/v2/2.5/RELEASENOTES.html
Squid-2.4 sends them as is, which causes troubles between Squid and the
helper on certain complex login names or passwords.
Regards
Henrik
tor 2003-07-10 klockan 14.52 skrev Hartmann.Josef Fa. secunet:
> Dear Henrik,
>
> I just found a new issue with squid 2.4Stable7 and 2.5Stable3.
>
> Users are authenticated by squid_rad_auth module. If a user has a rather "complex" passwords e.g. beginning with # character squid encodes those characters (as far as I can tell off by using strace). As I'm not a real programmer but would like to change that conversion back to a "real" character within squid_rad_auth could you tell me how to do that?
>
>
> Regards,
>
> Josef
-- Donations welcome if you consider my Free Squid support helpful. https://www.paypal.com/xclick/business=hno%40squid-cache.org Please consult the Squid FAQ and other available documentation before asking Squid questions, and use the squid-users mailing-list when no answer can be found. Private support questions is only answered for a fee or as part of a commercial Squid support contract. If you need commercial Squid support or cost effective Squid and firewall appliances please refer to MARA Systems AB, Sweden http://www.marasystems.com/, info@marasystems.comReceived on Thu Jul 10 2003 - 07:44:42 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:17:55 MST