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

Re: Editorial: ALTSVC HTTP/2 Frame.

From: Erik Nygren <erik@nygren.org>
Date: Thu, 8 Jan 2015 14:13:43 -0500
Message-ID: <CAKC-DJgUnb8J8kYZi=Ti7eT-=FiBaRoPM5eW9V4C6r-hODK7+A@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, Bence Béky <bnc@chromium.org>, HTTP <ietf-http-wg@w3.org>
What Martin suggests here makes sense to me.  Good catch, Bence.

On Thu, Jan 8, 2015 at 11:46 AM, Martin Thomson <martin.thomson@gmail.com>
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.
>
>
Received on Thursday, 8 January 2015 19:14:12 UTC

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