--- meeboo <[EMAIL PROTECTED]> wrote: > I'm kind of stumped on this problem too, how can I > send the original request uri to the login action so
> that it knows what page to redirect to? Which is the problem; getting the original request, or sending data to the action? Sending data to the action is easy; you can use an existing interface (like parameter aware, etc.) to pass a key/value, or you can create a new known interface (like setOriginalRequest or whatever) and use that. The OP had a few ideas for getting the original request, so I assume your question is passing the data? d. > Jae K wrote: >> I'm trying to implement a feature where a custom >> AuthenticationInterceptor would redirect the >> useragent to a login page, and then after the user >> logs in, he is redirected to the original request >> page. >> >> First, I have to send the original request path >> has a parameter to the login page or as a hidden >> field. To do this I plan to do one of the following. >> 1) use Redirect-Action with an OGNL param that >> looks like ${request.path}. I'm not familiar with >> OGNL so I'm not sure this will work >> 2) create a custom Redirect class that will use >> the HttpServletRequest and HttpServletResponse >> objects to send the original request path in the >> redirect URL. ____________________________________________________________________________________ Get your own web address. Have a HUGE year through Yahoo! Small Business. http://smallbusiness.yahoo.com/domains/?p=BESTDEAL --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]