Re: JSON headers from Cory Benfield on 2016-07-11 (ietf-http-wg@w3.org from July to September 2016)

From: Cory Benfield <cory@lukasa.co.uk>
Date: Mon, 11 Jul 2016 11:25:22 +0100
To: Andy Green <andy@warmcat.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Poul-Henning Kamp <phk@phk.freebsd.dk>, Yanick Rochon <yanick.rochon@gmail.com>, Phil Hunt <phil.hunt@oracle.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1E6AF297-8CF7-42BA-B3A6-0FFF1F4BCF2F@lukasa.co.uk>

> On 11 Jul 2016, at 08:15, Andy Green <andy@warmcat.com> wrote:
> 
> In the thread it seemed people discuss actual JSON formatted headers as
> a whole, ie, the whole header block becomes JSON.
> 
> I dunno there is any point to that, and it won't fly with HPACK.  But
> maybe I just misread what was suggested.

I don’t think anyone has suggested that. They have suggested making header field *values* entirely JSON, but no-one has suggested making the entire header block a JSON object as far as I have seen.

Cory

Received on Monday, 11 July 2016 10:26:00 UTC