[Zope] a login link

[Bryan C. Andregg]

--qlTNgmc+xy1dBmNv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 14, 2003 at 11:14:28PM +0100, Dieter Maurer mailed:
> Bryan C. Andregg wrote at 2003-3-14 08:58 -0500:
>  > This doesn't work. Or I should say, it half works. If the login is suc=
cessful,
>  > the page is returned but the user object hasn't been updated (has_role=
s()
>  > doesn't work) and subsiquent clicks of the link don't prompt for
>  > authentication.
>=20
> A typical HTTP authentication behaviour:
>=20
>   Login information is automatically send to the subhierarchy
>   rooted in the parent of the object that did require
>   the authentication.

I understand that, but if the client is sending the Login information and i=
t's
valid, then why doesn't Zope return the requested page using the login
information?
--=20
Bryan C. Andregg		Duke University Medical Center
 Programmer			Dept. of Anesthesiology
 e <bryan.andregg@duke.edu>
 p +1 919 684 6201

--qlTNgmc+xy1dBmNv
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD4DBQE+ddbxj9pElyS/cakRAm92AJUQTNp1hYtJK4rm3ljN6nEpOYDaAJ9emjTl
eI2Un4A4U+drFUzgYjfDGQ==
=YeF3
-----END PGP SIGNATURE-----

--qlTNgmc+xy1dBmNv--