Stephanie
Great - thanks for your help - the request generator
showed that the resource parameter was *not* set
and to fix it, I had to add:
<map:parameter name="use-request-parameters" value="true"/>
to the
<map:transform src="stylesheets/login.xsl">
Thanks
Derek
>>> [EMAIL PROTECTED] 2004/07/19 01:14:38 PM >>>
> No stupid questions here...!
>
> 1. How do I vaeify that the request-param
> "resource" *is* really set ??
>
Use the request generator at in your do-login pipeline instead of
map:redirect (and set the xml serializer). then you see all params and
values of the request.
> 2. If do not set the session propagator,
> then the URI to be displayed does not work, as
> it depends on those parameters to be set..
> What difference could/should it make?
>
> Thanks
> Derek
>
> >>> [EMAIL PROTECTED] 2004/07/19 12:41:20 PM >>>
>
> Might be a stupid question, but did you varify that the
request-param
> "resource" is really set when calling the login pipeline?
>
> Did you try without the session propagator?
It might get "erased" in between. Just and idea, the
"try-and-error"-stystem
of proplem solving has often worked for me. ;-)
cheers,
Stephanie
>
>
> > I am trying to redirect users, that click on a
> > protected page, back to that page after login:
> >
> > in the call to the login page, I have:
> >
> > login?resource=redirectpageuri
> >
> > (where redirectpageuri is the URI of the
> > protected page)
> >
> > The login page form has the necessary:
> >
> > <input type="hidden" name="resource" value="{$resource}"/>
> >
> > And the sitemap looks like:
> >
> > <map:match pattern="do-login">
> > <!-- try to login -->
> > <map:act type="auth-login">
> > <map:parameter name="handler" value="demohandler"/>
> > <map:parameter name="parameter_name"
> > value="{request-param:username}"/>
> > <map:parameter name="parameter_password"
> > value="{request-param:password}"/>
> > <!-- keep info in session -->
> > <map:act type="session-propagator">
> > <map:parameter name="myID" value="{ID}"/>
> > <map:parameter name="myTag" value="{tag}"/>
> > </map:act>
> > <map:redirect-to uri="{request-param:resource}"/> <!--DOES
> NOT
> > WORK? -->
> > </map:act>
> > <map:redirect-to uri="login"/>
> > </map:match>
> >
> > Regardless from where in the site the login page
> > is called, all that happens is the "home" page of
> > app is displayed ?
> >
> > Any ideas what else to change here??
> >
> > Thanks
> > Derek
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> > MailScanner thanks transtec Computers for their support.
> >
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> MailScanner thanks transtec Computers for their support.
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
