W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2001

Behavior of PUT on unlocked resource with invalid IF header ...

From: John Hall <johnhall@evergo.net>
Date: Tue, 14 Aug 2001 10:56:04 -0700
To: <ietf-dav-versioning@w3.org>
Message-ID: <001f01c124ea$633b4360$0300a8c0@xythosjohnhall>
If we reject it, then a client could detect that their previously active
lock had expired.

So ... I'm wondering if the spec should require the rejection.  I'm also
wondering if my implementation should reject it even in the spec is
silent.


-----Original Message-----
From: ietf-dav-versioning-request@w3.org
[mailto:ietf-dav-versioning-request@w3.org] On Behalf Of Jim Amsden
Sent: Sunday, August 12, 2001 5:24 PM
To: ietf-dav-versioning@w3.org
Subject: RE: Comments regarding locking & auto-checkin...


John asks:
Is a PUT supposed to be rejected if the IF header provided specifies an
invalid lock token and the resource is not locked?

The if header would likely be ignored since the resource isn't locked
and there's no token to check. But servers could implement this as a
failed If header since it doesn't match the resource. Looks like a
clarification might be needed in the spec.
Received on Tuesday, 14 August 2001 13:56:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:42 GMT