I've just come back to this thread as I'm just about to alter the
session handling in tha app that I'm working on. It currently uses
the url method, which I plan to replace.
I'm struggling to accept the form method, because as you say no more
a href=myapp.cgi?rm=next - unless of course we use
With the recent release of CAP::Authz 0.07, I've started going back through my
existing apps and updating them to use the authz_runmodes() instead of my
custom Authz plugins which did something similar.
While doing this, however, I've run into a scenario that I thought I'd ask for
some input
On Wed, Mar 5, 2008 at 4:47 AM, Mike Tonks [EMAIL PROTECTED] wrote:
I'm struggling to accept the form method, because as you say no more
a href=myapp.cgi?rm=next - unless of course we use javascript.
Now I like the old links, so cookies seems like a no brainer to me.
Can anyone explain
I haven't a clue on this one. I do the standard CA thing with page names:
?rm=home
?rm=contact
How do I do a URL re-write that makes the first one /home/ and the
second one /contact/ ?
Pointers would help...you don't have to give me the whole answer. I like
to learn. :-)
Robert
#
Robert Hicks wrote:
I haven't a clue on this one. I do the standard CA thing with page names:
?rm=home
?rm=contact
How do I do a URL re-write that makes the first one /home/ and the
second one /contact/ ?
CGI::Application::Dispatch. Not only will it let do URLs like that, but it will