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

Re: structured headers "why not JSON" FAQ

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 13 Jun 2018 18:38:06 +1000
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <A35D1D14-6FC5-4E8A-BA11-FD41B7EDEAE5@mnot.net>
To: "Julian F. Reschke" <julian.reschke@gmx.de>


> On 13 Jun 2018, at 6:33 pm, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> On 2018-06-13 10:01, Mark Nottingham wrote:
>> ...
>>> Please elaborate. What are the difficulties, and how is this different in structured headers?
>> How can you use ABNF to define the allowable structures in JFV? See the editors' draft of SH for an example there (a work in progress).
> 
> Precisely which part?

https://httpwg.org/http-extensions/draft-ietf-httpbis-header-structure.html#specify

> 
>>>>    Need to encode JSON to appear in HTTP headers, thereby making it not-JSON
>>> 
>>> Not true.
>> I'll change this to "Need to process JSON to assure that characters are escaped in a manner that's appropriate for HTTP headers."
> 
> Either that, or use a serializer where the encoding (and whitespace handling) can be configured.
> 
> <https://greenbytes.de/tech/webdav/draft-reschke-http-jfv-08.html#rfc.section.3>

See more recent revision.

Cheers,


--
Mark Nottingham   https://www.mnot.net/
Received on Wednesday, 13 June 2018 08:38:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:21 UTC