- From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Date: 2017年11月13日 08:30:44 +0200 (EET)
- To: Patrick McManus <mcmanus@ducksong.com>
- CC: HTTP working group mailing list <ietf-http-wg@w3.org>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Message-Id: <20171113063039.BD8E75DE56@welho-filter3.welho.com>
5. Using Extended CONNECT To Bootstrap The WebSocket Protocol https://tools.ietf.org/html/draft-mcmanus-httpbis-h2-websockets-02#section-5 " The Host information is conveyed as part of the :authority " pseudo-header which is required on every HTTP/2 transaction. 8.1.2.3. Request Pseudo-Header Fields https://tools.ietf.org/html/rfc7540#section-8.1.2.3 " To ensure that the HTTP/1.1 request line can be reproduced " accurately, this pseudo-header field MUST be omitted when " translating from an HTTP/1.1 request that has a request target in " origin or asterisk form (see [RFC7230], Section 5.3). Clients " that generate HTTP/2 requests directly SHOULD use the ":authority" " pseudo-header field instead of the Host header field. An " intermediary that converts an HTTP/2 request to HTTP/1.1 MUST " create a Host header field if one is not present in a request by " copying the value of the ":authority" pseudo-header field. So :authority is not required on *every* HTTP/2 transaction. / Kari Hurtta
Received on Monday, 13 November 2017 06:31:06 UTC