: Authentication and
Redirection
if you use a script/handler to create the login page,
and don't just serve up a static page, then you can use $r-prev-uri to
figure out what url triggered the 403, pass that to your authentication scheme
asa hidden field, and do whatever
Can anyone help me I have been scratching my head
with this problem for a while and I can't figure a solution out.
I have written a CGI script that is executed from
an ErrorDocument 403 so that when a user tries to access a secure web page from
the netthey are bounced to a welcome page and
Frawley
[mailto:[EMAIL PROTECTED]]Sent: Thursday, October 05, 2000
4:37 PMTo: [EMAIL PROTECTED]Subject: Authentication and
Redirection
Can anyone help me I have been scratching my head
with this problem for a while and I can't figure a solution out.
I have written a CGI script
AM
Subject: RE: Authentication and
Redirection
the eagle book has an example of this in chapter 6
(cookie based access control)
I've used an init handler to glean
$r-prev-uri and use that in the handler that implements the login page
for Apache-AuthCookie, which works
-From: Ian Frawley
[mailto:[EMAIL PROTECTED]]Sent: Thursday, October 05, 2000
5:29 PMTo: Geoffrey YoungSubject: Re: Authentication and
Redirection
I have looked at the example and tried to adapt,
the problem is that I will be serving WAP phones as well asPC's which
don't like cookies
The Ticket handling code in the Eagle Book shows how you can use
redirects and cookies to remember where the user wanted to go. After
authenticating, you redirect the user back to where they were trying to
go.
Which works, as long as you don't have to remember more than the URL the
user
