What do the wrapper classes actually do?
Is your Auth mechanism in them?
If not, how are you checking Auth?
Also, how does the filter know to avoid the request for the login page,
or the subsequent form submission?
If you're redirecting to a page that the filter applies to you'll end up
in a nev
I'm not seeing the complete sequence in your filter code, or even a
redirect. Should be something like:
doFilter(){
MyRequestWrapper reqWrapper = new MyRequestWrapper(servletRequest);
MyResponseWrapper respWrapper = new
MyResponseWrapper(servletResponse);
MyUserObj clientUser = MyU
Mani,
> What happens is that the login page is never displayed. I have validated
> the flow (using debugger) and it seems to be correct.
>
> So I was wondering if a response wrapper needs to do anything special in
> order to do a redirect.
Your wrapper looks okay to me, except that perhaps addi
Chris,
This is the complete sequence
1)User goes to a URL (say www.some-partner-site.com)
2)He selects our app link from there which redirects him to our site
(www.paybytouch.com)
3)Filter is applied on all url's
4)The filter has a wrapper class for both request and response.
5)The doFilter calls
Mani,
> The servlet class checks, if the user is authenticated using a variety
> of conditions. If the user is not authenticated, then the servlet sends
> a redirect to the login page.
>
> When debugging using Eclipse, I can see that my response wrapper class
> has the redirect url (http://my.com
