Re: PUT, If-Match, 412 - over-constrained?
Julian Reschke <julian.reschke@gmx.de> Sat, 15 June 2013 11:41 UTC
Return-Path: <ietf-http-wg-request@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 C244021F998F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 15 Jun 2013 04:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.932
X-Spam-Level:
X-Spam-Status: No, score=-9.932 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19RjX4ZvB93E for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 15 Jun 2013 04:41:49 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 364DA21F9B9B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 15 Jun 2013 04:41:49 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Unool-0005qH-Ir for ietf-http-wg-dist@listhub.w3.org; Sat, 15 Jun 2013 11:38:51 +0000
Resent-Date: Sat, 15 Jun 2013 11:38:51 +0000
Resent-Message-Id: <E1Unool-0005qH-Ir@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <julian.reschke@gmx.de>) id 1UnooQ-0005pI-RU for ietf-http-wg@listhub.w3.org; Sat, 15 Jun 2013 11:38:30 +0000
Received: from mout.gmx.net ([212.227.15.19]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <julian.reschke@gmx.de>) id 1UnooQ-0008H7-7l for ietf-http-wg@w3.org; Sat, 15 Jun 2013 11:38:30 +0000
Received: from mailout-de.gmx.net ([10.1.76.31]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MbNNK-1V4FlA140y-00In5t for <ietf-http-wg@w3.org>; Sat, 15 Jun 2013 13:38:04 +0200
Received: (qmail invoked by alias); 15 Jun 2013 11:38:04 -0000
Received: from p5DD94326.dip0.t-ipconnect.de (EHLO [192.168.2.117]) [93.217.67.38] by mail.gmx.net (mp031) with SMTP; 15 Jun 2013 13:38:04 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18i2bQ9q8Ui1YKc+TgzJ68LrsxMxxRZY1ww0Wcg0W o80/e2WJkUC6E1
Message-ID: <51BC5216.3050004@gmx.de>
Date: Sat, 15 Jun 2013 13:37:58 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Grzegorz Calkowski <grzes@vmware.com>
CC: ietf-http-wg@w3.org
References: <882266757.1630557.1361252309085.JavaMail.root@zimbra.com> <E1U7fx5-0000pd-Uo@frink.w3.org> <1014881229.176050.1361516997077.JavaMail.root@zimbra.com>
In-Reply-To: <1014881229.176050.1361516997077.JavaMail.root@zimbra.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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=-3.4
X-W3C-Hub-Spam-Report: AWL=-3.435, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1UnooQ-0008H7-7l 9971c72c891f485dc28d590b5dd2a542
X-Original-To: ietf-http-wg@w3.org
Subject: Re: PUT, If-Match, 412 - over-constrained?
Archived-At: <http://www.w3.org/mid/51BC5216.3050004@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18223
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 2013-02-22 08:09, Grzegorz Calkowski wrote: > > Hello, > > I found this old post by Roy at: > > http://tech.groups.yahoo.com/group/rest-discuss/message/10100 > > "A more interesting question is whether the spec over-constrains the > case where a PUT is successful but tried again. In other words, should > the server be allowed to accept the PUT if the etag differs but the > current state matches what is being PUT? Subversion handles such > cases nicely because it is common for two developers to patch the > same bugs. I think the "MUST respond with 412" is yet another case When two developers fix the same bug, how likely is it that they fix it *exactly* the same way? That seems to be a bit far-fetched unless it's a really really trivial bug. > of a bogus requirement being added in 2616. > > Note: this is an HTTP spec issue, not a REST issue. > > ....Roy" > > HTTPbis still requires 412 when the only thing that differs is etag. Any chance this will change? We could add a special case, but is this scenario happening frequently enough to justify that? best regards, Julian
- PUT, If-Match, 412 - over-constrained? Grzegorz Calkowski
- Re: PUT, If-Match, 412 - over-constrained? Julian Reschke