webdav

WebDAV Status Codes

HTTP status codes introduced by WebDAV (Web Distributed Authoring and Versioning) extensions. These supplement the standard HTTP status codes for distributed authoring operations.

8 codes

references rfc-editor.org/rfc/rfc4918

1xx Informational 1 codes

102 Processing Introduced by WebDAV (RFC 2518) to indicate the server has received and is processing the request, but has not yet completed it. Used for long-running WebDAV operations such as recursive COPY or MOVE to prevent clients from timing out.

2xx Success 2 codes

207 Multi-Status Defined by WebDAV (RFC 4918) to convey the status of multiple independent operations in a single response. The response body contains an XML document with individual `<D:status>` elements per resource, used by methods such as PROPFIND, PROPPATCH, COPY, MOVE, and LOCK when acting on multiple resources.
208 Already Reported Defined by RFC 5842 (DAV Binding Extensions) for use inside a 207 Multi-Status response to indicate that the binding's members have already been enumerated in a prior part of the same response and are not repeated. Prevents infinite loops when a resource is accessible via multiple DAV bindings.

4xx Client error 3 codes

422 Unprocessable Content Originally introduced by WebDAV (RFC 2518, section 10.3) to indicate that the request was syntactically well-formed XML but semantically invalid — for example, a PROPPATCH body containing unrecognised property values. Now adopted into the base HTTP specification (RFC 9110).
423 Locked Defined by WebDAV (RFC 4918) to indicate that the source or destination resource of a method is locked, and the request did not supply a valid lock token. Returned by methods such as PUT, DELETE, MOVE, COPY, and PROPPATCH when the target resource has an active write lock.
424 Failed Dependency Defined by WebDAV (RFC 4918) to indicate that a method could not be performed because the requested action depended on another action that also failed. Used within 207 Multi-Status responses to signal that operations on subsidiary resources were not attempted because a prerequisite operation failed.

5xx Server error 2 codes

507 Insufficient Storage Defined by WebDAV (RFC 4918) to indicate that the method could not be performed because the server cannot store the representation needed to complete the request. Commonly returned by PUT or COPY operations when the target collection or server volume lacks sufficient space.
508 Loop Detected Defined by RFC 5842 (DAV Binding Extensions) to indicate that the server detected an infinite loop while processing a WebDAV request, typically a PROPFIND with `Depth: infinity` traversing a collection that contains a circular binding back to itself.