- From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Date: Thu, 2 Feb 2017 18:44:59 +0200 (EET)
- To: HTTP Working Group <ietf-http-wg@w3.org>
- CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
https://tools.ietf.org/html/draft-ietf-httpbis-http2-encryption-10#section-2.1 | HEADERS | + END_STREAM | + END_HEADERS | :method = GET | :scheme = http | :path = /.well-known/http-opportunistic | host: example.com | | HEADERS | :status = 200 | content-type = application/json | DATA | + END_STREAM | [ "http://www.example.com", "http://example.com" ] To be consistent, host: example.com should be host = example.com But my question is that should this be :authority = example.com instead? This is client which generates HTTP/2 requests directly. 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). 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. / Kari Hurtta
Received on Thursday, 2 February 2017 16:45:36 UTC