I'm exploring Apache::AuthTicket, with fair success, but there is an element of it that I don't understand:
How is the login_screen method distinct from the login method? In the build tree for Apache-AuthTicket-0.31, there is a sample httpd.conf that contains (among other things): PerlSetVar FooLoginScript /foologinform <Location /foo> AuthType Apache::AuthTicket AuthName Foo PerlAuthenHandler Apache::AuthTicket->authenticate PerlAuthzHandler Apache::AuthTicket->authorize require valid-user </Location> <Location /foologinform> AuthType Apache::AuthTicket AuthName Foo SetHandler perl-script Perlhandler Apache::AuthTicket->login_screen </Location> <Location /foologin> AuthType Apache::AuthTicket AuthName Foo SetHandler perl-script PerlHandler Apache::AuthTicket->login </Location> What I don't understand is when are /foologinform and /foologin invoked? I thought this was the chain: request protected 'destination' -> yeilds form generated by /foologinform, action is '/foologin', 'destination' is a hidden field. sumbit '/foologin' -> authentication happens, cookie is sent with redirection to 'destination'. request 'destination' -> But I'm not seeing that happen. Can anyone clear this up? I can offer more details of my environemt, if anyone asks... -- Brian 'you Bastard' Reichert <[EMAIL PROTECTED]> 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path