You should check to see if you are able to get the parameters when the
request(s) is send via a "get" vs. a "post".
--- On Wed, 5/6/09, Sanjay Manchiganti wrote:
From: Sanjay Manchiganti
Subject: Re: j_security_check/j_username/j_password issue in Tomcat Version
6.0.
y, May 5, 2009 10:40:41 PM
Subject: RE: j_security_check/j_username/j_password issue in Tomcat Version
6.0.18
> From: Sanjay Manchiganti [mailto:ms4san...@yahoo.com]
> Subject: j_security_check/j_username/j_password issue in Tomcat Version
> 6.0.18
>
> Did anything change in terms of j_sec
> From: Sanjay Manchiganti [mailto:ms4san...@yahoo.com]
> Subject: j_security_check/j_username/j_password issue in Tomcat Version
> 6.0.18
>
> Did anything change in terms of j_securitycheck / container managed
> security between these two versions of tomcat?
What "two v
will get to the values in the request. Of course enabling this valve won't
cut if for production.
--- On Tue, 5/5/09, Sanjay Manchiganti wrote:
From: Sanjay Manchiganti
Subject: j_security_check/j_username/j_password issue in Tomcat Version 6.0.18
To: users@tomcat.apache.org
Date: Tuesday,
Hello All,
I've deployed two apps(say A and B) into two instances of Tomcat running on
port 8080 and 8081. They both have been enabled for form based
authentication.
Step 1: When a user tries to access the application A he is shown a
userid/password page(Alogin.jsp) with all the j_xxx detai
