tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ashok Venkat <>
Subject Re: j_security_check
Date Sun, 03 Feb 2008 19:18:27 GMT
Thanks for the detailed explanation, as you mentioned it seems that the second request is being
ignored ,but i am not clear how come the original request is matching with the second request?
The original is GET and the second one is POST? does tomcat compare just the URL strings?

----- Original Message ----
From: Konstantin Kolinko <>
To: Tomcat Users List <>
Sent: Sunday, February 3, 2008 9:39:41 AM
Subject: Re: j_security_check

You do

1) GET call
>            int_result = httpClient.executeMethod( getMethod );
The server caches your request and returns html page that contains the
login form.

2) POST call
>            postMethod = new PostMethod( "https://localhost:8444/j_security_check" );
>            int_result = httpClient.executeMethod( postMethod );
You imitate posting the login form. If the credentials are OK, tomcat answers
with a redirect to the original requested address (1).


3) When the next request comes, its url is compared against the one
that was requested at the first time. If there is a match, the
_original_ request is restored and processed, but the current one is

Thus your second POST is ignored and a cached copy of the first GET is
used instead.

You may want to look in the sources of
org.apache.catalina.authenticator.FormAuthenticator that does the

It is by design. I do not know what was wrong with 5.0 that your code
was working there.

You should change your code so that all the information be included
with the first call to TestServlet.

And the second call to the TestServlet can be changed to be a simple
GET, with no parameters. Or may be you can throw it away at all, if
you set "postMethod.setFollowRedirects(true);" on your post to

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message