BIND and HTTP status codes


while implementing WebDAV BIND in Jackrabbit [1] (the Apache Java 
Content Repository Reference Implementation), my colleague Manfred 
Baedke noticed that the spec currently micro-manages HTTP status codes: 
for instance, for a successful BIND it requires status codes of 200 or 
201, while - from an HTTP point of view - a 204 should be acceptable as 

Proposal: rephrase the text so that other success codes are acceptable 
as well, or remove the normative language completely, point to RFC2616, 
and rely on examples.

BR, Julian

[1] <>

Received on Friday, 26 September 2008 12:45:23 UTC