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

Re: FYI: JSON parsing

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 27 Oct 2016 11:05:02 +0200
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Mark Nottingham <mnot@mnot.net>, HTTP working group mailing list <ietf-http-wg@w3.org>
Message-ID: <b41122ed-b25a-7ce8-a3bf-331d9f916bad@gmx.de>
On 2016-10-27 11:00, Poul-Henning Kamp wrote:
> --------
> In message <e00a76b6-3b4b-6eb1-41a4-9214e93cdaf3@gmx.de>, Julian Reschke writes
> :
>> On 2016-10-27 09:29, Poul-Henning Kamp wrote:
>>> --------
>>> In message <B10FA80E-0A8E-4DBF-A400-963A582B7677@mnot.net>, Mark Nottingham wri
>>> tes:
>>>
>>>> For those who haven't seen it, this is a pretty deep dive on JSON
>>>> parsing ambiguities and mis-implementations.
>>>>
>>>>  http://seriot.ch/parsing_json.html
>>>>
>>>> Food for thought...
>>>
>>> Add to that thought that we cannot even use JSON to begin with, because
>>> of the restrictions on H1 headers...
>>
>> Sorry? Could you elaborate?
>
> "real" JSON can contain newlines

Yes, but it's not relevant whether we can transport random JSON. What's 
relevant is that all JSON can be converted to something that can be 
safely transmitted in HTTP/1.1 header field values (and that is the case).

Best regards, Julian
Received on Thursday, 27 October 2016 09:05:47 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 October 2016 09:05:49 UTC