It looks like Tomcat3Response.endHeaders needs to call coyoteResponse.setContentLength so that Http11Processor can see it. It might also want to call setContentType, but that one doesn't seem to be used by the Http11Processor. ----- Original Message ----- From: "Keith Wannamaker" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 03, 2002 3:55 PM Subject: [3.3.2-dev] CoyoteConnector2 invalid headers
> When using CC2 with TC 3.3.2, every request sets both > the content-length and the transfer-encoding, which > is not only wrong, but can confuse some clients. > > Content-Length: 9 > Transfer-Encoding: chunked > > The 4.0 org.apache.catalina.connector.http.HttpConnector > does not have this problem. Any quick ideas while I dig > through the code? > > Keith > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
