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

Re: FYI: JSON parsing

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Thu, 27 Oct 2016 09:00:51 +0000
To: Julian Reschke <julian.reschke@gmx.de>
cc: Mark Nottingham <mnot@mnot.net>, HTTP working group mailing list <ietf-http-wg@w3.org>
Message-ID: <66657.1477558851@critter.freebsd.dk>
--------
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

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Thursday, 27 October 2016 09:01:26 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 October 2016 09:01:31 UTC