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=17014>.
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=17014

ServletResponse.flushBuffer() no longer commits the response

           Summary: ServletResponse.flushBuffer() no longer commits the
                    response
           Product: Tomcat 4
           Version: 4.1.18
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Connector:Coyote HTTP/1.1
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


ServletResponse.flushBuffer() no longer commits the response (writing status 
code and headers) as specified in the Servlet spec ...

> public void flushBuffer() throws java.io.IOException
>
> Forces any content in the buffer to be written to the client. A call 
> to this method automatically commits the response, meaning the status 
> code and headers will be written. 

Presumably this was lost in the transition from HttpConnector to 
CoyoteConnector.  This can be fixed by altering 
org.apache.coyote.tomcat4.CoyoteReponse.

> public void flushBuffer() throws IOException {
>
>     // NEW *****
>     if  ( !isCommitted() )
>         coyoteResponse.sendHeaders();          
>     // *********
>
>     outputBuffer.flush();
> }

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to