DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3612>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3612 ------- Additional Comments From [EMAIL PROTECTED] 2001-09-14 09:31 ------- This works for me, every single time, with any combination of extra path info or not, and query string or not. There are unit tests in our test suite that validate this behavior as well. The way that invoked servlets are handled, the only time such a bug could happen is on the very first request to a particular servlet -- the first time in, the invoker servlet sets up a direct servlet mapping (/servlet/foo/*) for servlet "foo" that is used from then on, so the results will always be consistent. Do you have a reproducible test case for this? If not, I'm going to have to resolve it with status WORKSFORME ...
