-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
Mark Thomas wrote:
| Many of securityfilter's users use it merely because it allows
| drive-by logins. We're happy to have them (!), but this seems like
| a reasonable feature to have in the core of Tomcat.
|
| Given there is a demand for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin,
Martin Gainty wrote:
| ..I'll ask the dumb question..what is a drive-by login
Sorry for the colloquialism. By drive-by login, I mean that the user
was presented with a login page that was not served by Tomcat as a
result of a request for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tokajac,
Tokajac wrote:
| But when i submit the (activated) username and password, i got the
| --
| HTTP Status 408 - The time allowed for the login process has been
exceeded.
|
Christopher Schultz wrote:
Tokajac,
Tokajac wrote:
| But when i submit the (activated) username and password, i got the
|
--
| HTTP Status 408 - The time allowed for the login process has been
exceeded.
| If you wish to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
Mark Thomas wrote:
| If you go directly to the login page Tomcat can't tell the difference
| between that situation and when you go to a protected page, are
| redirected to the login page and then take so long to log in the session
| times out
Christopher Schultz wrote:
Mark,
Mark Thomas wrote:
| If you go directly to the login page Tomcat can't tell the difference
| between that situation and when you go to a protected page, are
| redirected to the login page and then take so long to log in the session
| times out (the page you need
