> -----Original Message----- > From: Olivier GUCKERT [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 28, 2003 5:22 PM > To: Cocoon-user > Subject: Re: auth problem > > > > > Martin Dulisch a écrit : > > > > Hi Olivier, > > > > protection works over the 'auth-protect' action. You can use it in any > > pipeline. So you dont need a redirect to protect other pages. > > > > Martin > > Ok Martin and thanks > > But, if i write : > <map:match pattern="login"> > <map:act type="auth-login"> > <map:parameter name="handler" value="MaProtection"/> > <map:parameter name="parameter_nom" > value="{request-param:nom}"/> > <map:parameter name="parameter_mot-de-passe" > value="{request-param:mot-de-passe}"/> > <map:redirect-to uri="annu2.xml"/> > </map:act> > <!--L'authentification a échoué --> > <map:redirect-to uri="login-page"/> > </map:match> > > The first seen page after login is always annu2.xml... This is of course because of your redirect statement. Usually, if your login-page is called it gets a request parameter named "resource" that contains the protected resource. So, you have to take care that you pass this parameter (e.g. via a hidden input field) to your login pipeline. Then you can do a redirect to {request-param:resource}.
Carsten --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
