WebDAV return codes
The table below describes the possible return codes for WebDAV requests against namespaces.
Code | Meaning | Description |
200 | OK | GET, HEAD, PROPPATCH, or LOCK: HCP successfully completed the request. |
201 | Created | PUT, MKCOL, COPY, or MOVE: HCP successfully completed the request. (For COPY or MOVE, no object existed at the target location.) |
204 | No Content |
COPY, MOVE, or DELETE: HCP successfully completed the request. (For COPY or MOVE, a deletable object existed at the target location.) GET, HEAD, or DELETE of custom metadata: The specified object exists but does not have a default annotation. |
206 | Partial Content | GET: HCP successfully retrieved the data in the byte range specified in the request. |
207 | Multi-status | PROPPATCH, PROPFIND, or DELETE for a directory: The operation generated multiple return codes. The response body contains an XML document that shows the return codes and the names of the objects to which they apply. |
400 | Bad Request |
All methods: The request is not well-formed. Correct the request and try again. PROPPATCH or PROPFIND: The request XML is invalid. PUT: For a request to add or replace custom metadata, the namespace is configured with custom metadata XML checking enabled, and the request includes custom metadata that is not well-formed XML. COPY or MOVE: The request does not specify the full URL for the target location. |
403 | Forbidden |
For all methods, one of:
MKDIR: You cannot create a directory in the specified location. PROPPATCH: The requested change is not allowed. COPY or MOVE: The specified source and destination locations are the same. DELETE: The specified object is under retention. |
404 | Not Found | GET, HEAD, PROPPATCH, PROPFIND, COPY, MOVE, DELETE, LOCK, or UNLOCK: HCP could not find the object, metafile, or directory specified in the request. |
405 | Method Not Allowed |
MKCOL: HCP could not create the directory because it already exists. DELETE: HCP could not delete the specified object or |
409 | Conflict |
PUT: HCP could not store the object because it already exists. PUT, MKCOL, COPY, or MOVE: One or more directories in the target path do not exist. PROPPATCH: HCP could not store dead properties as custom metadata because the default annotation contains custom metadata. |
412 | Precondition Failed |
COPY or MOVE: The operation failed because either:
LOCK: HCP could not lock the specified object. |
414 | Request URI Too Long | All methods: The portion of the URL following data or metadata is longer than 4,095 bytes. |
416 | Requested Range Not Satisfiable |
GET: For a byte-range request, either:
|
423 | Locked | PUT, PROPPATCH, COPY, MOVE, DELETE, or LOCK: HCP could not perform the requested operation because the target object is locked. |
500 | Internal Server Error |
All methods: An internal error occurred. Try the request again, gradually increasing the delay between each successive attempt. If this happens repeatedly, please contact your tenant administrator. |
503 | Service Unavailable |
One of:
In either case, try the request again, gradually increasing the delay between each successive attempt. |
507 | Insufficient Storage |
PUT: Not enough space is available to store the object. Try the request again after objects are deleted from the namespace or the namespace capacity is increased. PROPPATCH, MKCOL, or COPY: Not enough space is available to complete the request. Try the request again after objects are deleted from the namespace or the namespace capacity is increased. |