- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 11 Jul 2016 21:11:09 +0200
- To: Willy Tarreau <w@1wt.eu>
- Cc: 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>
On 2016-07-11 21:01, Willy Tarreau wrote: > On Mon, Jul 11, 2016 at 08:05:32PM +0200, Julian Reschke wrote: >> On 2016-07-11 19:44, Poul-Henning Kamp wrote: >>> -------- >>> In message <aa9cee9c-d8e3-17ba-9fcd-e327575cd5a8@gmx.de>, Julian Reschke writes >>> : >>> >>>> 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... >> >> You can't rely on how a JSON parser reports or that it rejects duplicate >> fields. > > Guys, I still don't understand why it would not work if everything is > considered to be a list. A list can be ordered, right ? Inside a JSON *object*, the wire format allows multiple instances of the same key (member name), and the recipient behavior for these cases is undefined. Best regards, Julian
Received on Monday, 11 July 2016 19:12:06 UTC