Hi everybody, thanks for your replies.
> -----Original Message----- > From: Mark Thomas [mailto:ma...@apache.org] > > Chunked encoding does not mean that the output is unbuffered. If a > client declares support for HTTP/1.1 then web servers are free to use > chunked encoding for the response if they choose. Hi Mark, you're right: It seems Tomcat actually uses a buffer for the response. But it seems a bit strange to me that it uses chunked encoding, although the content length should be known when sending the headers as the response fits into the buffer. I agree that Tomcat itself is not violating the spec. However what is not compliant to the spec, are that 304 responses that I get from IIS when using the ISAPI redirector 1.2.31 (with chunked encoding enabled) with Tomcat 7.0.6 (and this time for normal 304 responses, not the ones from bug #50413 ;) ), because they contain a "Transfer-encoding: chunked" header and a body (as described in bug #50363). This worked fine with Tomcat 7.0.5. I will have to disable the chunked encoding support in the ISAPI redirector in order to get spec-compliant 304 responses (because then they will have a "Connection: close" header without a body) until the 1.2.32 connectors are released. > -----Original Message----- > From: André Warnier [mailto:a...@ice-sa.com] > > There have a been another couple of threads recently related to the > chunked transfer-encoding. > If I remember correctly, in one of them the OP complained about Tomcat > using this encoding > for small responses, on the grounds of the added overhead or bandwidth > introduced by the > chunk headers. > I am not sure that I agree with the basic principle (as the transfer- > encoding is really > the server's or intermediate agent's decision), but say in the interest > of keeping the peace : Hello André, Well I do not want to disable chunked encoding. I clearly prefer a "Transfer-encoding: chunked" header over a "Connection: close" header when the content length is not known in advance, because with chunked encoding the connection can stay open, whereas with a "Connection: close" the connection has to be closed after the response is finished. That's why I want to use the ISAPI redirector with chunked encoding enabled; however this regression is preventing me from doing this, as it would cause invalid 304 responses (and I can't compile the trunk version of the Connectors by myself, so I have to wait until 1.2.32 gets released or the regression in Tomcat is fixed). Again, thanks for your replies. Cheers Konstantin Preißer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
