Normally, with filters you chain when you're finished, not redirect. The only time you would redirect would be if the user wasn't logged in and you wanted to redirect to your login page and then a plain ol' redirect should work fine as long as you don't redirect to a page that's also under the protection of your filter. (*Chris*)
On 10/4/06, Don Brown <[EMAIL PROTECTED]> wrote:
Sounds like you have the situation under control - you are probably forwarding to an /admin/ action. As for the redirect, from a servlet filter, a plain redirect is the best approach. Don On 10/4/06, Garner Shawn <[EMAIL PROTECTED]> wrote: > I have a filter and I'm trying to check a session value is set for security. > I'm putting my filter to the /admin/* url mapping. > > My filter is getting hit but then if I try to do a redirect to a > struts action it seems like I get some kind of infinite filter loop > and is choking, I'm kind of new is there something that would do this? > > Hmm, now I am thinking about it maybe I'm accidently including the > /admin/ in the redirect. I'll check. > > Also I was just using a plain request dispatcher to forward. > Is there a struts specific on I should be using? > > Thanks, > Shawn > > --------------------------------------------------------------------- > 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]
