W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Fri, 25 Jul 2014 01:52:32 +1200
Message-ID: <53D10FA0.60109@treenet.co.nz>
To: ietf-http-wg@w3.org
On 25/07/2014 1:15 a.m., Martin Thomson wrote:
> I'll fix the description of :path.
> 
> On 24 July 2014 03:34, Kari Hurtta wrote:
>> OPTIONS http://some.host HTTP/1.1
>>
>> seems translate to
>>
>>  :method    = OPTIONS
>>  :scheme    = http
>>  :authority = some.host
>>  :path      = *
> 
> That's a fun one, isn't it?  I'll see what I can do there.  The number
> of "except when..." clauses in this protocol continues to surprise
> (and depress) me.
> 

That seems to be an invalid mapping in Karis' example.

The input 1.1 URI has a path-empty pattern (0<pchar>), but the h2 being
generated shows a path-rootless segment pattern.

The recipient of that 1.1 request is supposed to assume path value of
"/" in these cases not "*".

So IMHO there is nothing new that need be said. The 1.1->2 gateway maps
:path to either empty value or to "/" same as any 1.1 intermediary would.

Amos
Received on Thursday, 24 July 2014 13:53:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 9 September 2019 17:48:20 UTC