RE: DeltaV methods on locked non-VCR: which response code?

For RFC-3253, the intent was to use 405 as a generic response
when there wasn't anything more specific you could (or wanted)
to say, and use 403/409 when you wanted to give details.

So an RFC-3253 client would only expect a DAV:error node in a
403 or 409 response.

Cheers,
Geoff

-----Original Message-----
From: Pill, Juergen [mailto:[email protected]]
Sent: Thursday, August 01, 2002 11:54 AM
To: 'Clemm, Geoff'; '[email protected]'; Nevermann, Dr., Peter
Subject: RE: DeltaV methods on locked non-VCR: which response code?


Hello,

In case of 405 would you expect the response body to contain a packed
(DAV:must-be-checked-out, DAV:must-be-checked-in, etc.) or an empty response
body?

Best regards

Juergen







 -----Original Message-----
From: 	Clemm, Geoff [mailto:[email protected]] 
Sent:	Wednesday, July 31, 2002 23.01 PM
To:	'[email protected]'
Subject:	RE: DeltaV methods on locked non-VCR: which response code?


   From: Nevermann, Dr., Peter [mailto:[email protected]]

   assume
   1) a non-collection *non-VCR* resource at /foo.xml which is *locked*
   2) an ordinary collection resource at /bar which is *locked*.

   We are wondering what the response status code should be in these
particular
   cases (403, 409, 423, ???):

   CHECKOUT /foo.xml

405

   CHECKIN /foo.xml

405

   LABEL /foo.xml

405

   REPORT /foo.xml

Depends on the report request.  Since a report is a read-only
operation, it doesn't matter that it is write-locked.

   UPDATE /foo.xml

405

   VERSION-CONTROL /foo.xml

423

   MKWORKSPACE /bar

403, with DAV:resource-must-be-null in the DAV:error node.

Cheers,
Geoff