RE: Status code for creating lock-null resource

Granted a client cannot tell the difference as you state *if* they took no
preceding action.

However, I don't think the spec should be changed:

1) Obviously it would go against the definition in RFC 2616 for 201 Created.
2) You haven't actually created a resource. An LNR doesn't physically exist,
you've only reserved the "name". You have created a lock, but that is not
the same thing.
3) Doesn't make sense to me to get a "201 Created" response for a successful
LNR, then if you tried to DELETE or GET it for example, get a 404 or 405 (as
per RFC 2518 sec 7.4).
4) Might break existing applications etc.

Alternatively, a client could perform one of a number of actions to discover
that the resource didn't exist before they attempt to LOCK it (create the
LNR) and get a 404.

Side notes - results when creating an LNR with:

5) mod_dav pre v1.0 (think v0.9.16) returns a 200 OK response.
6) IIS 5.0 (on Win2K) returns a 201 Created response.

Regards

Shaun Hall
Xerox Europe

> -----Original Message-----
> From: Lisa Dusseault [mailto:lisa@xythos.com]
> Sent: 14 June 2001 17:54
> To: Webdav WG
> Subject: Status code for creating lock-null resource
> 
> 
> 
> RFC 2518 seems to want 200 OK for the response to a LOCK 
> request.  However,
> that means clients can't tell the difference between a lock 
> of an existing
> resource and the creation of a LOCK-null resource.  Shouldn't 
> 201 Created be
> returned if a lock-null resource is created?
> 
> lisa
>

Received on Friday, 15 June 2001 05:16:33 UTC