If you are using 2.0, checkout this thread http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2442326.
There is an excellent example attached by Thierry Boileau. The key for me was to realize that you can "guard" a router and attach your requests to the gaurded router. As for redirection look at the org.restlet.Response class, there are a few redirection methods there. On Tue, Feb 9, 2010 at 5:43 PM, kevinpauli <[email protected]> wrote: > I am currently evaluating technologies for a new web app and I'm intrigued > by > Restlet. There's a particular behavior I need, and I'm curious as to > whether Restlet, with its high degree of configurability, provides a means > of achieving this. > > When receiving any authenticated request, I'd like to be able to run some > custom logic to check password expiration and, if the password sent matches > the old value but is expired, redirect the user to the appropriate URIs for > changing his password, rather than returning a 403. If the password sent > does not match the old value, then I want to return the 403. > > Naturally I'd like to be able to configure this once, site-wide, and not > require every restlet to repeat this logic. Is there a well-established > pattern in Restlet for achieving this? > -- > View this message in context: > http://n2.nabble.com/How-to-route-all-authenticated-requests-through-some-custom-logic-tp4544754p4544754.html > Sent from the Restlet Discuss mailing list archive at Nabble.com. > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2446277 > -- Erick Fleming ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2446289
