- From: Barry Leiba <barryleiba@computer.org>
- Date: Tue, 23 Dec 2014 12:21:49 -0500
- To: Semyon Kholodnov <joker.vd@gmail.com>
- Cc: RFC Errata System <rfc-editor@rfc-editor.org>, Roy Fielding <fielding@gbiv.com>, Julian Reschke <julian.reschke@greenbytes.de>, Pete Resnick <presnick@qti.qualcomm.com>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
> that the rules prohibit the following scenario: an HTTP/1.1 proxy > sends an HTTP/1.1-request to an HTTP/1.0-server (the proxy knows by > some means that the server is an origin server of HTTP/1.0 version) > with "Connection: keep-alive" header, the server sends an > HTTP/1.0-response with "Connection: keep-alive" header in it. > > This response is current, and the bullets mandate that the connection > will close after receiving it: the first bullet doesn't apply since > the "close" option is not present, second bullet doesn't apply because > the received protocol is HTTP/1.0, the third bullet does not apply > since the recipient *is* a proxy, and thus the final bullet "The > connection will close after the current response" applies. I think you're wrong, and I was trying to convey that before. The third bullet does apply, because the recipient is not a proxy: it's a server. The initiator is a proxy; the recipient is not. These bullets are talking about request/response transactions, not about individual response messages. I think that's made clear in the paragraphs that precede the bullets. Roy and Julian should, of course, weigh in on this, though. Barry
Received on Tuesday, 23 December 2014 17:22:23 UTC