-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dick,
On 4/6/2011 2:52 AM, Dick Eastlake wrote: > Here's an access log from an unsuccessful login using Chrome. Note > the post to j_security_check returns a 200 even though the > id/password entered was a valid one. Response code 200 means "OK". There is nothing wrong with a 200 response to that request. What response code were you expecting? 401? That would result in a nasty error message being shown by your client. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2cmQcACgkQ9CaO5/Lv0PD4DQCgv4lkfgPwT1+9zk72wGYq7whJ U8MAnRdiJ6weJZm+G3qd4aWDqS0RJ6IE =bRyD -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
