On 01/29/2009 04:10 PM, Henrik Nordstrom wrote:
> Note: HTTP isn't really designed for content transforming proxies, and
> many things gets a little shaky in such environment. gzip/deflate by
> proxies is really intended to be done as a content-encoding which isn't
> plagued by any of this (as it's transport hop-by-hop, not entity
> end-to-end), unfortunately support for that hasn't really been picked up
> anywhere significant..
You meant "done as transfer-encoding", right?
Alex.
> Second note: The message body looks fully identical if you compare a
> "Transfer-Encoding: gzip, chunked" message to a "Content-Encoding: gzip"
> "Transfer-Encoding: chunked" message in HTTP/1.1. The difference is in
> headers..
>
> Third node: Transfer-Encoding is only valid within HTTP/1.1 and can not
> be used in HTTP/1.0.
>
> Regards
> Henrik
Received on Fri Jan 30 2009 - 15:09:34 MST
This archive was generated by hypermail 2.2.0 : Fri Jan 30 2009 - 12:00:04 MST