Just a point worth if it's related to FORM login; The form login does
have a maximum request size that is stored in user session and restored
after login as original request. If request was too big (fileupload,
article submissions, etc), it might get dropped. I think the default max
is about 100K.
Also, check it's not the user having something like fasterfox or another
web "accelerator" installed. Those are agressive and can sometimes mess
up navigation.
As also suggested, if you have apache front end, check it does not have
some special configuration that would drop parameter at some point. And
check there is no proxy / active firewall that could badly alter request...
And check it's not simply user typing "enter" in url bar to refresh a
POST page :)
Christopher Schultz a écrit :
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arjan,
M4N - Arjan Tijms wrote:
It's a good thought, and such a thing could have happened. Only in this
case the parameters are already missing before any request processing is
being done.
No, your filter will only be executed after the login has been handled,
since Tomcat's authentication is done using a valve, which is processed
before any filters.
If you are experiencing it yourself directly, you can verify that it
happens even when a login is not involved.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG0yf79CaO5/Lv0PARAuXEAJ9+knXYy6mNmilh2dgWeSfmRoT/OACeI8ev
63G7rl+mlc5glAWDnuhxM7M=
=hb97
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
