Michael: It is great to see custom_error(). Last time, it took me a few hours in hacking the whole module. :-(
> > However, I dont think it will work for his problem because his javascript code > seems to launch a NEW REQUEST, thus loosing anything that was stored away in > $r->subprocess_env(). So the only viable option is to pass the error codes in > they url (as part of the query string) I think. > An extra cookie is another solution. Peter Bi ----- Original Message ----- From: "Michael Schout" <[EMAIL PROTECTED]> To: "Peter Bi" <[EMAIL PROTECTED]> Cc: "Fran Fabrizio" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, April 19, 2002 9:44 AM Subject: Re: framesets/AuthCookie question > On Wed, 17 Apr 2002, Peter Bi wrote: > > > Fran: > > > > You may need to 1) add a few lines of code in AuthCookie to make your error > > code aware to other methods, and 2) have a dynamic login page that can > > interpret the code. Alternatively, you may try AccessCookie I posted. :-) > > The CVS version of AuthCookie has a custom_errors() hook in it that does this > sort of thing. > > However, I dont think it will work for his problem because his javascript code > seems to launch a NEW REQUEST, thus loosing anything that was stored away in > $r->subprocess_env(). So the only viable option is to pass the error codes in > they url (as part of the query string) I think. > > Mike > >
