W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Re: HTTP Request+Response issues

From: James M Snell <jasnell@gmail.com>
Date: Wed, 24 Apr 2013 11:15:20 -0700
Message-ID: <CABP7RbfjQnThCEoE9h8V8=o5NsGUxPew2YyFPmAx4OGGU8syVA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Done. Now: https://github.com/http2/http2-spec/issues/69

On Wed, Apr 24, 2013 at 11:02 AM, Martin Thomson
<martin.thomson@gmail.com> wrote:
> I think that this is right.  You ultimately have to reach the
> conclusion that responses are in the same stream as the request, but
> that should be express, not implied.
>
> James, can you create an editorial issue in the github repo?  We (the
> editors) will get to it when we can.
>
> On 24 April 2013 09:58, James M Snell <jasnell@gmail.com> wrote:
>> Reading through the current draft, unless I missed it, it needs to be
>> clarified that HTTP request and responses MUST be sent within the same
>> stream unless we specifically want to allow responses to be sent in a
>> different stream than the request.
>>
>> For instance:
>>
>> Request:
>>   Stream-ID: 1
>>   :method: get
>>
>> Response:  (server uses the same stream)
>>   Stream-ID: 1
>>   :status: 200
>>
>> OR...
>>
>> Request:
>>   Stream-ID: 1
>>   :method: get
>>
>> Response: (server uses a different stream)
>>   Stream-ID: 2
>>   :status: 200
>>
>> Currently, it appears that this is an unspoken assumption in the spec
>> text that needs to be called out explicitly. Or, if it's already
>> there, it needs to be made more visible.
>>
>> - James
>>
Received on Wednesday, 24 April 2013 18:16:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:10 UTC