On Tue, 2002-08-27 at 00:59, Henrik Nordstrom wrote:
> Transfer-encoding is a slightly different question. Entirely different rules
> apply as Transfer-encoding is a hop-by-hop property, not a property of the
> object entity like content-encoding is. Transfer-encoding is purely a
> business between Squid and the HTTP server (or peer cache) or between Squid
> and the requesting client. In that sense Transfer-encoding is a safer
> playfield than Content-encoding..
This gets into the architecture issues - that Adrians code goes a long
way (but not completely) to correcting. My client streams code also
helps a lot. Transfer-encoding throws off all the object length and
offset calculations in squid, too many of which all access a single
struct without any actual tracking of octets through a given point in
the request flow. This is what killed the prior TE implementation -
Range requests could SNAFU the store if the server->squid connection
used TE.
Anyway, this is off-topic for the mod-gzip list :}.
Rob
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:16:10 MST