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?


Received on Thursday, 14 June 2001 12:56:23 UTC