RE: [SQU] Passing Username, Password and URL to authenticate prog ram

From: Kieran Skinner <>
Date: Wed, 24 Jan 2001 11:39:24 -0000

Hi Rob,

Basically I want to accelerate for multiple servers, with different users
able to access different servers.

The accelerated servers are on a mish mash of different hardware/software
platforms so it will be easier for me to manager the user access centrally,
through squid and a user database. Hopefully, this will also mean that the
skills requird to administer the webservers may be lower.

Henrick pointed out that the Redirector helpers would recieve both username
and url. So I guess I could authenticate username and password with an
authentication program, then use the redirector to redirect the user to an
error page if they try to access a server they are not supposed to. This
could work but would be a bit messy.

Maybee there are some other tricks to give me this functionality.


-----Original Message-----
From: Robert Collins []
Sent: 23 January 2001 21:11
To: Kieran Skinner;
Subject: Re: [SQU] Passing Username, Password and URL to authenticate

Why do you need to? If you are looking to tie the username, password and url
together you will not be following the guidlines from
rfc2617 for basic authentication)
. If you are looking at getting digest authentication running, the front end
code is already present on sourceforge... feel free to
jump in a write a directory integrated backend.


----- Original Message -----
From: "Kieran Skinner" <>
To: <>
Sent: Wednesday, January 24, 2001 12:04 AM
Subject: [SQU] Passing Username, Password and URL to authenticate program

> Is it possible to pass the requested URL to a custom athentication program
> in addition to the username and password supplied.
> --
> To unsubscribe, see

To unsubscribe, see
To unsubscribe, see
Received on Wed Jan 24 2001 - 04:42:25 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:57:33 MST