- From: Roland Zink <roland@zinks.de>
- Date: Sat, 15 Mar 2014 22:25:48 +0100
- To: ietf-http-wg@w3.org
In principle this is true. If compression is loosing the content-length then this may amplify the existing issue. Transferring entity information like content-length (if it is known) in addition to transport properties (like the compressed content-length) may help, but may cause issues if the information is inconsistent / wrong. Roland On 14.03.2014 23:33, Julian Reschke wrote: > On 2014-03-14 23:04, William Chan (ιζΊζ) wrote: >> It's unfortunate, but I agree that given the interop issues, I don't >> think we can require this. > > HTTP/1.1 already REQUIRES the ability to process chunked encoding. > What we're talking about is adding gzip. Streaming/buffering shouldn't > be any more issue than it already is in 1.1. > > > ... > > Best regards, Julian >
Received on Saturday, 15 March 2014 21:26:11 UTC