Quoting "Craig R. McClanahan" <[EMAIL PROTECTED]>:
> On Wed, 30 May 2001, Craig R. McClanahan wrote:
>
> > Hello Paul,
> >
> > This definitely sounds like something wrong with Tomcat 4 -- most
> likely a
> > combination of things related to the browser (which can affect which
> HTTP
> > version is in use), your filters, and the ultimate servlet or JSP
> page
> > being called. To help narrow things down a bit:
> > * Do you have a small test case we can use to investigate this?
> > If so, you can send it either to TOMCAT-DEV or to me in private
> mail.
> > * Are your clients using HTTP/1.0 or HTTP/1.1?
> > * Does your filter create a wrapper on the servlet response, or is it
> > just passing things through?
> >
> > I suspect that somewhere along the line the output stream isn't
> getting
> > flushed or closed in a timely manner -- the above information will be
> > helpful to be able to identify where.
> >
> > Craig
>
> I just added some more unit tests that do output filtering, and they
> all
> work immediately. I now more strongly suspect that this problem is
> related to some combination of using HTTP/1.1, the particular filters
> and
> wrappers being executed, and Tomcat not flushing something somewhere
> when
> it is supposed to -- but a real-life example would be tremendously
> helpful
> in tracking it down further.
I suspect it's a special case problem. I quickly tried with the FilterExample
in the examples webapp (which does not actually wrap anything), and it works ok.
Remy
