"Tomcat Users List" <tomcat-user@(protected):
>Well, first thing to check is to see if the request contains the params(I
>would think it would, otherwise you are using a malfunctioned
>web-client:).
>Burp Proxy is one of the nice tools I can think of that allows you to
>examine requests and responses.

I think what you are saying is to examine the stream before Tomcat gets
it? The problem is that this behavior is rather rare - I can't just make
it happen and it's never happened on my development system. I suppose I
could log everything to a file. Does burp proxy have a timestamp for the
requests? The screenshots don't show it. I'd be hard to track it down if
it didn't have a timestamp.

>Well, first thing to check is to see if the request contains the params(I
>would think it would, otherwise you are using a malfunctioned
>web-client:).
Actually, I am suspicious of the browser/network. If I view the stream and
the parameter is not present, either the browser is errant or the packet
is lost on the network, no?

> Secondly, I hope you didn't have any
>sendRedirect in your framework. Because you will lose the original
>request,
>and its params if you use a redirect.

I assume you mean a redirect that occurs before I check for the existence
of my EOF parameter? No, my framework checks for EOF before any redirect
is possible.

Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@(protected)


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)