W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

RE: New Version Notification for draft-kazuho-early-hints-status-code-00.txt

From: Mike Bishop <Michael.Bishop@microsoft.com>
Date: Tue, 1 Nov 2016 22:22:05 +0000
To: Cory Benfield <cory@lukasa.co.uk>
CC: Julian Reschke <julian.reschke@gmx.de>, Kazuho Oku <kazuhooku@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <BN6PR03MB2708CF5ADA4D5DDCF7F6B88E87A10@BN6PR03MB2708.namprd03.prod.outlook.com>
Shouldn't matter, for us.  I'll defer to others.

-----Original Message-----
From: Cory Benfield [mailto:cory@lukasa.co.uk] 
Sent: Tuesday, November 1, 2016 3:08 PM
To: Mike Bishop <Michael.Bishop@microsoft.com>
Cc: Julian Reschke <julian.reschke@gmx.de>; Kazuho Oku <kazuhooku@gmail.com>; HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: New Version Notification for draft-kazuho-early-hints-status-code-00.txt


> On 1 Nov 2016, at 17:24, Mike Bishop <Michael.Bishop@microsoft.com> wrote:
> 
> FWIW, our implementation should already ignore this response and process the final status code correctly.  If you have a public endpoint that returns a hint, we can all do a quick field test.

Were you interested in a HTTP/1.1 or HTTP/2 endpoint? I can put one up that unconditionally returns a 103, though it may just be easier to spin up H2O or nghttp2.

Cory
Received on Tuesday, 1 November 2016 22:22:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 November 2016 22:22:46 UTC