- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Mon, 11 Jul 2016 18:27:52 +0000
- To: Yanick Rochon <yanick.rochon@gmail.com>
- cc: Julian Reschke <julian.reschke@gmx.de>, Phil Hunt <phil.hunt@oracle.com>, HTTP Working Group <ietf-http-wg@w3.org>
-------- In message <CAB0No9mkFB7FS89_roz3CDDfASGwEN-8n_6kP040zEo_b5Jh_A@mail.gmail.com> , Yanick Rochon writes: >--001a113ec7849c5bac05375ff43b >> >b) relying on the uniqueness is a problem anyway (due to how JSON works). >> >> Sorry, but I have no idea what you are saying there... >> >I believe he is saying that standardized JSON parsers do not care for >duplication in JSON properties, and simply overwrite any previous values, >which is as defined in the specs and an expected behaviour, which does not >resolve the issue at all. As long as no implementation prefers the first key/value pair, that does resolve the "smuggling" issue. >I personally would favor a strict enforcement, where a duplicated key >should generate errors, but this is agains the specs... I'm still confused, which specs say you can have duplicate keys ? -- 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 Monday, 11 July 2016 18:28:18 UTC