IETF Logo Mail Archive

Re: JSON headers

Julian Reschke <julian.reschke@gmx.de> Mon, 11 July 2016 11:18 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 D958412D125 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 11 Jul 2016 04:18:27 -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 cU0n7J3O0SIH for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 11 Jul 2016 04:18:26 -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 C4C9912B04D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 11 Jul 2016 04:18:26 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bMZA9-0006QT-7H for ietf-http-wg-dist@listhub.w3.org; Mon, 11 Jul 2016 11:14:09 +0000
Resent-Date: Mon, 11 Jul 2016 11:14:09 +0000
Resent-Message-Id: <E1bMZA9-0006QT-7H@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) 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 1bMZA5-0006PL-Uk for ietf-http-wg@listhub.w3.org; Mon, 11 Jul 2016 11:14:05 +0000
Received: from mout.gmx.net ([212.227.17.22]) by maggie.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1bMZA0-00065l-VM for ietf-http-wg@w3.org; Mon, 11 Jul 2016 11:14:04 +0000
Received: from [192.168.1.123] ([5.10.171.186]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MgKoE-1bj1Pc1NjS-00NlXg; Mon, 11 Jul 2016 13:13:26 +0200
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
References: <74180.1468000149@critter.freebsd.dk> <A17D3EFD-A935-4971-BCF6-DC9D38302CAD@oracle.com> <564a72e8-b9d3-1f9c-5982-48f2b07272e5@greenbytes.de> <3924.1468137899@critter.freebsd.dk> <683f5f58-6046-d9fb-cc75-d0ab3890ce23@greenbytes.de> <4105.1468141779@critter.freebsd.dk> <5cdf0fa8-063c-7eaa-a9e3-fb6db7417254@gmx.de> <4213.1468143913@critter.freebsd.dk> <94e4a5c2-3465-fef3-6221-d9f4fcccb5fa@gmx.de> <4324.1468145426@critter.freebsd.dk> <CAB0No9kf6gje3Tc+impphV5tUHjksCkL1PJ1YAgNjXO+tLq=XA@mail.gmail.com> <176d58df-debf-e660-edf7-7d686c926ef6@gmx.de> <5939.1468189218@critter.freebsd.dk> <40e62f5c-9fe4-35c0-d986-c01fb63f6b4e@gmx.de> <8251.1468229350@critter.freebsd.dk> <e9a55629-656c-3b6a-3ac4-5fb7a109b2f0@gmx.de> <8739.1468234635@critter.freebsd.dk>
Cc: 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: <38b3e7bb-3202-f489-ff15-d4d545e13ca0@gmx.de>
Date: Mon, 11 Jul 2016 13:13:26 +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: <8739.1468234635@critter.freebsd.dk>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:0REjEinfY7jY+36M8MK5jt0ZmM7FfjSLzU0Dxr/RZlXf+4GGjFL tmiiTUikzWJlob/HF6tzobBOYPZXFzkhpeVSE7a4+bYE+jrOpas0z7cmxxOvdQRY6tmE5oH yRc02GCnJdqwclsuaP2ithQ0HGs7jvhQL0ki0G46BBLaUYS5uWLOVDinnNz50kFXafGofwS kczVkyTeaWb5haGnX/r3w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:oexdUQ3HLnA=:Zg/9jTF+lYSm2Sz/zReGF+ IB9ljRm2QEkY++XCKx/Zu3j18EqWhmEQ6H1UEo7MJUEEviW54IY+ibRF4YquddAh1TYPlEVZi q0yCFHiElwdCgWp8hdfk3c4U7WAw5OdoSm+bJvH0vdgun2xSlMv7mkyYDsrolhiFYYx7zuSII VgtT7MFyg+1XE4Yz6ctj5fo3FtFgyqJ5eInofWUXLhiLk+UHozXyAPZaoL5e34Bwkx3Z22gcX m+Z6XAFFH+9xQq5smUeBO5bL+RrYXkvcrLIzeLUqHYR31xZEVD8XDzNJh3e5nC4J9pjVrKvoE DhhJrZF846pO5sfQ4oMalyp/xmpNLWgksCgPwBryNz67sa6mKKj+6+p41ep7JkMntONeC/j28 eRMP5gUW6h7wv+i2SkwtYuCNZXvQITchjPoMACWXjsAVmarPV/BTE+YP9Jz0OXg6viCPOnLMt XzSv8f4YUw8ejRNy4c/LQE7C0SzDXFp/cUaz1kYpJ6+2YWVlGnXusVyBrr51ElcQX/ga/mkhb n1mU5tv2hZBPs+o995nHfBhH9tg2pSGOSUZ++/f6HicIwLvA0ObomDVu274B9BtEstPpxoobt OQahseRhhCR4iOdRoHqMkSQs/KMQdswSR4lySAFX3PWHqJ8bwvLzzXA2G0BQ79afN5PN9VscY SbiyoShxIlDHlprQbkCglqlvKUwhD9y8DcTTKGvON66bm6ZAlpERWHXe5WJQI06qqZlZTSdxx AfoZedN9CHTy+q0uTK/F7G5ckbL0uXZZnVqdwqkbIaY0tpL+KbqV+dAKKo3YC6rFMMCm6iIIl ExuMNuc
Received-SPF: pass client-ip=212.227.17.22; 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.100, 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: maggie.w3.org 1bMZA0-00065l-VM c0e4961ab42c6890ee4860af22303fbb
X-Original-To: ietf-http-wg@w3.org
Subject: Re: JSON headers
Archived-At: <http://www.w3.org/mid/38b3e7bb-3202-f489-ff15-d4d545e13ca0@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31894
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 12:57, Poul-Henning Kamp wrote:
> ...
>> It may not have been a good idea in the first place, but that's what we
>> currently have in HTTP, both 1.* and 2. I'm arguing that it's better to
>> live with it, and to make things as consistent as possible with respect
>> to this.
>
> I couldn't possibly disagree more.
>
> We should eliminate and sunset as many of the warts of HTTP as we
> reasonably can, in order to make it an easier and more efficient
> protocol to understand and implement.
> ...

Maybe. But this is a complex change, and it will be hard to deploy.

The intent of this draft was to describe something that works today with 
the semantics we have.

Both are interesting things to do; I just believe that requiring to do 
both things at the same time is likely to kill the effort, or delay it 
significantly.

> In particular, I find it very unintuitive that we would ever constrain
> the JSON formats utility, in order to retain a misfeature like
> repeated headers.

How exactly is it "constrained"?

Best regards, Julian

v2.23.0 | Report a Bug | By Email