[This question seems more appropriate for the users list rather than the developers list.]
On Wed, 5 Mar 2003, Andrew Ho wrote: > I am dealing with a broken proxy which understands chunked > Transfer-Encoding on the proxy to server side, but does the wrong thing on > the proxy to client side (it sends the "Transfer-Encoding: chunked" header > from the server to proxy response, but sends the content unchunked). > > The easiest fix seems to be to always respond with an HTTP/1.0 response. I > tried adding "SetEnv force-response-1.0 Yes" to the Apache server, but if > Apache gets an HTTP/1.1 request (which it does in this case), it continues > to send an HTTP/1.1 response. Additionally setting downgrade-1.0 didn't > change anything. > > Is there a way to force Apache to send an HTTP/1.0 response even in > response to an HTTP/1.1 request? The short answer: no. The long answer: using downgrade-1.0 will, in fact, force Apache to treat the request as if it was HTTP/1.0. It will therefore use only HTTP/1.0 features in the response. But it will still respond with HTTP/1.1 in the response line, since this just declares it as an HTTP/1.1 capable server; it doesn't mean the response itself uses HTTP/1.1 features. force-response-1.0 does cause apache to declare itself as HTTP/1.0, but it will only do so if the client request uses HTTP/1.0. force-response-1.0 does nothing if the client uses HTTP/1.1. See: http://httpd.apache.org/docs/env.html#special Joshua.
