IETF Logo Mail Archive

Re: JSON headers

Julian Reschke <julian.reschke@gmx.de> Mon, 11 July 2016 19:16 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0056812B064 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 11 Jul 2016 12:16:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.208
X-Spam-Level:
X-Spam-Status: No, score=-8.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TEgqXvAg4_Qu for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 11 Jul 2016 12:16:33 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9FFB12B065 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 11 Jul 2016 12:16:29 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bMgcj-00073F-UV for ietf-http-wg-dist@listhub.w3.org; Mon, 11 Jul 2016 19:12:09 +0000
Resent-Date: Mon, 11 Jul 2016 19:12:09 +0000
Resent-Message-Id: <E1bMgcj-00073F-UV@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1bMgcf-00072K-Vf for ietf-http-wg@listhub.w3.org; Mon, 11 Jul 2016 19:12:06 +0000
Received: from mout.gmx.net ([212.227.15.19]) by lisa.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1bMgce-0006ho-0B for ietf-http-wg@w3.org; Mon, 11 Jul 2016 19:12:05 +0000
Received: from [192.168.178.20] ([93.217.94.167]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0LmKOI-1amnct1322-00ZxrA; Mon, 11 Jul 2016 21:11:09 +0200
To: Willy Tarreau <w@1wt.eu>
References: <8251.1468229350@critter.freebsd.dk> <e9a55629-656c-3b6a-3ac4-5fb7a109b2f0@gmx.de> <8739.1468234635@critter.freebsd.dk> <38b3e7bb-3202-f489-ff15-d4d545e13ca0@gmx.de> <8854.1468236033@critter.freebsd.dk> <326f0b93-dbd5-3dfb-2a35-d1bf084684b4@gmx.de> <9221.1468245597@critter.freebsd.dk> <aa9cee9c-d8e3-17ba-9fcd-e327575cd5a8@gmx.de> <9801.1468259070@critter.freebsd.dk> <15d27f23-6b51-1e8e-3f10-194c80570424@gmx.de> <20160711190107.GB9542@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>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <0e467573-4f68-80a5-14a4-5a63b41ac4d4@gmx.de>
Date: Mon, 11 Jul 2016 21:11:09 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160711190107.GB9542@1wt.eu>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Lxg6l9P/NUM9AxmMoQED3fWV7CLeJNH0ocYPyOGlyPWVtyqw2s/ SzH5T6GLrLJWVAv9MUAKMT/6IkfFRtmjs/OK4shutnp19iuHkR6mpkf0fMFxoTxHPyqDmAb 1fHW2aRZQ7bDbzM3vwNQnGMfkYBoJJK0mB3SYxDjtGHlqJqtCA+9i5GlCHGgnvk41q7bSG8 jG4JuEUfLVm5gLm8rvXig==
X-UI-Out-Filterresults: notjunk:1;V01:K0:nDWq4uxCOUY=:sAH5sBh9QSnYnW2bdQVd6d LeWG11ddNZaoisbn0sMECUvPfzMcTnq/b/S7bvGs0/dL/PRbVpb95FMVsKI1SGEduFqs7Ib1G Rf/A7vgIlbl6IqwoDqAfqJTAUdCwKpW79GZSNXKVjuEsZgVRfPHjUVO0aRkrbP5E6GGqH4zhU EuSx2xtEgOsLUvOicPIWWof6tEVleu8wW4Q74BZaYNrrSm3U40sZ4VEf5oslphbVW+yYAvoXr bLkY11Y5nR1r/lUZeXWJZ52K5ssFMyaQeHgbAOuqzokGCfLqtVCEUbGXEE6OELckGYHfMUIkw ET0zKZG1ZlJGc7MJYxcBowCjSQToIZwUz99b7gbt+PGicfMZFy6DETa5xGaycGDzjPkrifyx7 /HsKGeOUdHxW8ZKRQYWM2/HrTmLovbMENEKaFkmaPwjR724xLmaQRbNAnX/irfqsC6j9EVOjh zuF86vsVXbQb0boTKDlRN1I/lV/0yzDCwBkp8btIcMRQvNWX+qr47BwINfiACsvC4b9j/Cd+K id6glUBgEwLGUcEBmOIFqSoV2n+zLFinWk2UTEKP1xUhI6fDYIGchwdxpS5ybWzl5GSQrK/Z9 nq2jjMfFhUVlrOqUs34zy+EJd+ET6DJ2LmMuTMgUCP1cPK62wEGVCOmgke3+bPGfuIGE5rMtd 1uQKUvNAj1czxD8+rOykRAA43x5LvZFr9MNBwmNp+Hc1QDJGUK2fsPda7kfUviz+1ZkFC8wUm AFbWejj799VmUrDbLS4pRCUSVL0VLXMrLym6B8OeXEZ1gSAWuhk6FiQmCI6NbsKjsMvPav2G0 mH9Zlbn
Received-SPF: pass client-ip=212.227.15.19; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-6.7
X-W3C-Hub-Spam-Report: AWL=-0.077, BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1bMgce-0006ho-0B 4ba7ce05093705ca0d71f531799537d3
X-Original-To: ietf-http-wg@w3.org
Subject: Re: JSON headers
Archived-At: <http://www.w3.org/mid/0e467573-4f68-80a5-14a4-5a63b41ac4d4@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31908
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

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

v2.23.0 | Report a Bug | By Email