On Sun, Dec 28, 2008 at 12:08 AM, Mark Hedges <hed...@scriptdolphin.org> wrote: > > On Sat, 27 Dec 2008, Mark Hedges wrote: >> Hi, I'm trying to figure out how to preserve the request >> body across an OpenID login redirect cycle. >> ... >> But when they come back from the OpenID server, how do I put >> the saved request body or post params into the new request?
To persist data across http requests you either need to use cookies or stash the data in $r->connection->pnotes (less reliable, only use if you understand your application connection handling details). > On another note, is there any way to do a proper Authen > handler with an in-line login form, instead of popping up a > klunky browser authentication prompt? I always use Apache2::AuthCookie (or my own subclass). Authentication really comes down to code that sets $r->user; there are various layers such as cookies to bridge the gaps but the Apache directives such as Require-User are referring to $r->user. And look at the PerlAuthHandler, PerlFixupHandler, and PerlAuthzHandler phases. Is this part of Apache2::Controller? An Apache2 based framework with OpenID support sounds appealing.
