I've never done a request dumper before, but is there a way to trigger it only if Tomcat is going to issue a 400?
Sorry for replying to my own posting, but for JSP urls, we do seem to know that request.getScheme() for example returns null when things are bad, though I'm not sure how a bad request even makes it to my JSP if it's truly malformed.
Could I use that somehow so do the request dumper aspect? I need a few pointers for doing it, but it sounds like I need to install some code that would check for the scheme being null and then do something else to cause the request to dump.
Is that right? Is that a possible approach I should take? The issue is this is a customer system so we cannot make changes but in the evenings when they are not using it and then it probably will have to run all day before it can be removed later.
Thanks for any tips! --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
