Jess Holle wrote:
Tim Funk wrote:
Section 5.5 of the spec:
When a response is closed, the container must immediately flush all
remaining content in the response buffer to the client. The following
events indicate that the servlet has satisfied the request and that
the response object is to
Dan Johnsson wrote:
Jess Holle wrote:
Tim Funk wrote:
Section 5.5 of the spec:
When a response is closed, the container must immediately flush all
remaining content in the response buffer to the client. The
following events indicate that the servlet has satisfied the request
and that the
First, I'd like to say that we should *not* consider the following issue
as one to prevent a stable label for Tomcat 5.0.16.
That said, I've noted that if you do:
response.setContentLength( 0 );
All subsequent setHeader(), etc, calls are ignored -- Tomcat considers
the response commited.
Section 5.5 of the spec:
When a response is closed, the container must immediately flush all remaining
content in the response buffer to the client. The following events indicate
that the servlet has satisfied the request and that the response object is to
be closed:
The termination of the
Tim Funk wrote:
Section 5.5 of the spec:
When a response is closed, the container must immediately flush all
remaining content in the response buffer to the client. The following
events indicate that the servlet has satisfied the request and that
the response object is to be closed:
The
