On Fri, Jun 4, 2010 at 6:10 AM, "Plüm, Rüdiger, VF-Group" <ruediger.pl...@vodafone.com> wrote: [...] > Isn't that what Transfer-Encoding is designed for?
Yes, and in fact if we were talking about a brand new protocol, I'd probably argue in favor of putting the compression specifier in the Transfer-Encoding. I think a change in the semantics of Content-Encoding in HTTP/1.1 might be a way to obtain similar benefits without breaking existing software. -Brian
