On Fri, Jul 26, 2002 at 11:46:45AM -0400, [EMAIL PROTECTED] wrote: > In case anyone is interested, here are some captures taken with Sniffer > Pro. The key things to note are that Apache 2.0.39 mod_proxy drops the > Content-Length header, and also that it inserts "Content-Type: > text/plain". This behaviour is causing Web-Polygraph to report > superfluous errors.
Section 13.5.2 of 2616 seems to have some thoughts on this, but the wording seems a bit muddled. A Content-Length is a end-to-end header (generally non-modifiable), and 13.5.2 says: The Content-Length field of a request or response is added or deleted according to the rules in section 4.4. A transparent proxy MUST preserve the entity-length (section 7.2.2) of the entity-body, although it MAY change the transfer-length (section 4.4). I believe it would be possible for the proxy to delete the content-length header and replace it with another mechanism of its choosing to signal the entity-length. But, the question is whether we want to also send the C-L (if known) when doing a connection close. That's an option. As far as adding Content-Type, section 13.5.2 says: A proxy MUST NOT modify or add any of the following fields in a message that contains the no-transform cache-control directive, or in any request: ... - Content-Type ... I'm not sure how to parse the 'or in any request' bit. Does that apply to all requests or just those with no-transform cache-control set? If it is free to modify it, then I think I can make a case that the DefaultType directive applies. But, I'm not 100% sold on that, either. -- justin
