Derek Yes, such a prefix is a bit unhandy, but it isn't that big problem. Perhaps someone knows a better solution.
The redirection URI is specified in the handler configuration part, so you don't have to put it in the pipeline: http://cocoon.apache.org/2.1/developing/webapps/authentication.html#The%2BConfiguration%2Bof%2Ba%2BHandler Maik On Wednesday 14 July 2004 10:45, Derek Hohls wrote: > Mark > > Yes, this makes sense, although its a little clunky > (having to add a prefix to all protected URIs, which > would cause existing URIs to "break" if you later wanted > to move them from unprotected to protected status) - > but the document does not say how to handle redirects > in this case - can I say: > > <map:match pattern="protected-*"> > <map:act type="auth-protect"> <!-- protect the resource --> > <map:parameter name="handler" value="myhandler"/> > > <map:match pattern="protected-first"> > <map:generate src="resource1.xml"/> > <map:transform src="toHTML"/> > <map:serialize/> > </map:match> > > <map:match pattern="protected-second"> > <map:generate src="resource2.xml"/> > <map:transform src="toHTML"/> > <map:serialize/> > </map:match> > > </map:act> > > <!-- something was wrong, redirect to login page --> > <map:redirect-to uri="login"/> > > </map:match> > > Thanks > Derek > > >>> [EMAIL PROTECTED] 2004/07/14 10:20:51 AM >>> > > Hi Derek, see: > > http://cocoon.apache.org/2.1/developing/webapps/authentication.html#Multipl >e%2Bprotected%2Bdocuments > > > > Best Regards, > > Maik > > On Wednesday 14 July 2004 08:26, Derek Hohls wrote: > > I know its possible to protect a document > > by checking for a valid login... > > > > <map:match pattern="protected"> > > <map:act type="auth-protect"> > > <map:parameter name="handler" value="demohandler"/> > > <map:generate src="docs/protected.xml"/> > > <map:transform src="stylesheets/simple-page2html.xsl"/> > > <map:serialize/> > > </map:act> > > <!-- something was wrong, redirect to login page --> > > <map:redirect-to uri="login"/> > > </map:match> > > > > But is it possible to protect an entire pipeline in > > the same way... and how can one handle redirects in > > this instance (assuming its the same for the whole pipeline)? > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
