Christopher Schultz wrote:
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.
Of course, but that's exactly what I'm saying. If Tomcat's auth code
runs first, than the possible error would be in Tomcat's code.
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.
The custom authentication method is filter based. I installed the filter
that prints the request parameters to the log as the very first filter
in the chain; this means it gets called before any other filter does.
So, the logging is the very first piece of my code that gets called when
processing a single request.
Like I said earlier: in the AJP connector the parameters are there and
at the first opportunity that my own code can run they are gone. They
get lost somewhere in between. Since none of my code runs in between,
it's hard to say what happens. I might try building a debug Tomcat that
does some extra logging at key points in the request handling, but for a
high volume production server this would really be my last resort.
Kind regards,
Arjan Tijms
--
It's a cult. If you've coded for any length of time, you've run across someone
from this warped brotherhood. Their creed: if you can write complicated code,
you must be good.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
