PUT, If-Match, 412 - over-constrained?

Grzegorz Calkowski <grzes@vmware.com> Fri, 22 February 2013 07:11 UTC

Resent-Date: Fri, 22 Feb 2013 07:10:45 +0000
Resent-Message-Id: <E1U8mmL-0002dL-J1@frink.w3.org>
Date: Thu, 21 Feb 2013 23:09:57 -0800
From: Grzegorz Calkowski <grzes@vmware.com>
To: ietf-http-wg@w3.org
Message-ID: <1014881229.176050.1361516997077.JavaMail.root@zimbra.com>
In-Reply-To: <E1U7fx5-0000pd-Uo@frink.w3.org>
References: <882266757.1630557.1361252309085.JavaMail.root@zimbra.com> <E1U7fx5-0000pd-Uo@frink.w3.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Thread-Topic: PUT, If-Match, 412 - over-constrained?
Thread-Index: Fhd7VSLZ3pgX1itlvlR1ksYWGcvXuw==
Received-SPF: none client-ip=208.91.2.23; envelope-from=grzes@zimbra.com; helo=edge02-zcs.vmware.com
Subject: PUT, If-Match, 412 - over-constrained?
Archived-At: <http://www.w3.org/mid/1014881229.176050.1361516997077.JavaMail.root@zimbra.com>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

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
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?

Thanks,
Grzegorz

PUT, If-Match, 412 - over-constrained? Grzegorz Calkowski
Re: PUT, If-Match, 412 - over-constrained? Julian Reschke