On Thu, 26 Feb 2004, Jon Kay wrote: > Content-Encoding > > New HttpHdrContCode module, that parses related HTTP headers, and > arranges > for encoding or decoding appropriately. To be called from > clientProcessRequest, cacheHit, and processReplyHeader.
This really should build ontop of the Client Streams framework rather than hardcode into the processing. See programmers guide chapters on Client Streams. I think you will find this fits quite nicely for Content-Encoding requirements. Exacly where to add the logics on when to stack the content-encoding client stream pipe onto the reply path is another question. Regards Henrik
