- From: Adrien de Croy <adrien@qbik.com>
- Date: Thu, 14 Jun 2007 13:05:39 +1200
- To: Travis Snoozy <ai2097@users.sourceforge.net>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
Hi soprry if I wasn't clear, I'm actually talking about case where HTTP/1.1 client sends HTTP/1.1 request to HTTP/1.1 proxy, which sends request through another HTTP/1.1 proxy which goes then to an HTTP/1.0 origin server. the client and first proxy will receive an HTTP/1.1 response from the proxy closest to the origin server (if it replies with its own version). this means the client and first proxy do not learn the true version of the origin server. Adrien Travis Snoozy wrote: > On Thu, 14 Jun 2007 12:48:22 +1200, Adrien de Croy <adrien@qbik.com> > wrote: > > <snip> > >> However, a proxy server that always responds with its own supported >> version number will break some of these mechanisms. >> > <snip> > > That's why it's not allowed. Section 3.1: > > Proxy and gateway applications need to be careful when forwarding > messages in protocol versions different from that of the application. > Since the protocol version indicates the protocol capability of the > sender, a proxy/gateway MUST NOT send a message with a version > indicator which is greater than its actual version. If a higher > version request is received, the proxy/gateway MUST either downgrade > the request version, or respond with an error, or switch to tunnel > behavior. > > So, if you access an HTTP/1.1 server through a HTTP/1.0 proxy, sorry -- > you're stuck with HTTP/1.0. > >
Received on Thursday, 14 June 2007 01:05:25 UTC