W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2015

Re: Editorial: ALTSVC HTTP/2 Frame.

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 08 Jan 2015 18:04:13 +0100
Message-ID: <54AEB88D.3000708@gmx.de>
To: Martin Thomson <martin.thomson@gmail.com>
CC: Bence Béky <bnc@chromium.org>, HTTP <ietf-http-wg@w3.org>
On 2015-01-08 17:46, Martin Thomson wrote:
> On 8 January 2015 at 08:22, Julian Reschke <julian.reschke@gmx.de> wrote:
>> It can contain what the header field contains, and that allows specifying
>> the authority (uri-host and port).
>>
>> Am I missing something?
>
> It would seem so.
>
> The header field doesn't contain origin information because that is
> derived from the request.  The header field says: "for requests to
> *the origin of this request*, please send here: list of service
> endpoint tuples"; when the frame is sent on stream 0, it lacks that
> context.
>
> I suggest that you define the frame as length (sadly, 255 bytes isn't
> long enough to hold the longest conceivable origin string) plus origin
> plus the remainder being exactly the same as the Alt-Svc header field.

I see. Thanks for the explanation.

An alternative would be to put it into an "o" parameter (to be ignored 
in the header field). Or resurrect draft-reschke-http-jfv and switch to 
JSON...

Best regards, Julian
Received on Thursday, 8 January 2015 17:04:51 UTC

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