-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Arjan,
M4N - Arjan Tijms wrote: > Christopher Schultz wrote: >> 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. > > I see. The thing is, I'm not using any container managed authentication > at all. All authentication is handled by the application. Oh, well, that's different, then ;) > But even if I > used the container's (Tomcat's) authentication, then it still would be > Tomcat's code than ran before my code, right? Uh, I'm not really sure what you're saying, here. TCs auth code /will/ run before any of your code if you are using it. Since you're not, your own auth code will run whenever you have configured it to do so. Do you implement authentication and authorization as a filter? Or, do you have something else going on? I'm asking because it's possible your own authentication mechanism has a bug or two that is somehow killing the request parameters. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG1CG79CaO5/Lv0PARAnCgAJ4pAKGKhNWpnd1FMl1vut8flBZ+MACgglvW otYD3KMYiEZ7kw4dDuMs+dI= =tPZ6 -----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]
