- From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Date: Thu, 1 Dec 2016 20:04:50 +0200 (EET)
- To: Alex Rousskov <rousskov@measurement-factory.com>
- CC: HTTP working group mailing list <ietf-http-wg@w3.org>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
https://tools.ietf.org/html/rfc7540#section-8.1.2.3 | o The ":authority" pseudo-header field includes the authority | portion of the target URI ([RFC3986], Section 3.2). The authority | MUST NOT include the deprecated "userinfo" subcomponent for "http" | or "https" schemed URIs. | | 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). There is "MUST be omitted" https://tools.ietf.org/html/rfc7230#section-5.3.1 | 5.3.1. origin-form | | The most common form of request-target is the origin-form. | | origin-form = absolute-path [ "?" query ] > Do you think the RFC examples should use ":authority" instead of "host"? There should be "native" http/2 only examples also. Now these are HTTP/1.1 to HTTP/2 conversion examples, where ":authority" is not allowed. / Kari Hurtta
Received on Thursday, 1 December 2016 18:05:28 UTC