WebDAV Protocol Errors

[versie: maandag 16 juni 2003]

The following table lists the error codes returned by the Microsoft Exchange 2000 Server WebDAV protocol service. Along with each error code or group of codes are the names of associated HTTP methods and a description of each error code.

Error Code Method Description
All 100 level codes * Informational
100 Continue [HTTP]   Initial part of incomplete request was accepted by server. [HTTP]
101 Switching Protocols [HTTP]   Server wants to switch to a newer version, or real-time protocol, to continue. Used when an Upgrade header was in the client request. [HTTP]
102 Processing [WEBDAV] MOVE, COPY Can be used to indicate status of ongoing processes, particularly processes that use the Depth header. This is to avoid having the client time-out with an error. [WEBDAV]
All 200 level codes * Success
200 OK [HTTP] GET, HEAD, OPTIONS, LOCK, POST, DELETE Typical successful response for these methods, in cases where no new resource is created. [HTTP]
  SUBSCRIBE, UNSUBSCRIBE Possible success response.
  TRACE Trace was reflected back to sender [HTTP]
  PROPFIND, PROPPATCH Possible successful response if all props were successfully returned or set. Not used in Microsoft implementations, see code 207. [WEBDAV]
201 Created [HTTP] POST, PUT Resource successfully created [HTTP]. If the action cannot be completed immediately, a 202 must be returned instead. [HTTP1.1]
  MKCOL, MOVE Collection successfully created or resource successfully moved. [WEBDAV]
  MKREF Reference successfully created.
  LOCK If you do a LOCK on a null resource, the LOCK will create the resource.
202 Accepted [HTTP] DELETE, PUT, POST Resource will be created or deleted but it has not yet been created or deleted [HTTP].
203 Non-authoritative Information [HTTP] Any? Meta-information in the header did not come from origin server. Used only when response would otherwise be 200 OK. [HTTP] Use of this response code is not required. [HTTP1.1]
204 No Content [HTTP] POST, PUT Standard success response when no resource was created [HTTP]. The server has fulfilled the request but does not need to return an entity-body, and might want to return updated meta information. [HTTP1.1]

With PUT, the 204 response allows the server to send back an updated etag and other entity information about the resource that has been affected by the PUT operation. This allows the client to do the next PUT using the If-Match precondition to ensure that edits are not lost.

  DELETE, UNLOCK Standard success response. [WEBDAV]
  COPY, MOVE The source resource was successfully copied or moved to a pre-existing destination resource. [WEBDAV]
205 Reset Content [HTTP]   Server has fulfilled request and client should reset document view. Must not include an entity. [HTTP]
206 Partial Content [HTTP] GET Only some of the resource was returned, with Range header to indicate how much. [HTTP]
207 MultiStatus [WEBDAV] PROPFIND, PROPPATCH, SEARCH, MKCOL Typical successful response. [WEBDAV]
  SUBSCRIBE, UNSUBSCRIBE Typical successful response.
  COPY, MOVE If an error in executing the COPY occurs with a resource other than the request URI, then the response must be 207. 424 and 201 responses should NOT be values in 207 multistatus responses to COPY. [WEBDAV]
  LOCK Used with a multiresource lock request. [WEBDAV]
All 300 level codes * Redirection– (further action must be taken to complete request)
300 Multiple Choices [HTTP] GET, HEAD The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location. [HTTP]
301 Moved Permanently [HTTP] GET, HEAD New permanent URI has been assigned to resource. [HTTP]
  PUT Server wishes to apply the PUT to a different URI than the one in the method.
302 Moved Temporarily [HTTP] GET, HEAD New temporary URI has been assigned to resource. [HTTP]
302 Found [HTTP1.1] GET, HEAD, other The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. [HTTP1.1]
303 See Other [HTTP] POST Typically used to respond to a POST, because a response to a POST cannot be stored in the cache, but the response to a GET can. Client uses GET to see other. [HTTP]
304 Not Modified [HTTP]   If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The response MUST NOT contain a message-body. [HTTP]
305 Use Proxy [HTTP] Any The requested resource MUST be accessed through the proxy given by the Location field. [HTTP1.1]
306 Unused   The 306 status code was used in a previous version of the specification and is no longer used; in addition, the code is reserved. [HTTP1.1]
307 Temporary Redirect [HTTP1.1] GET, HEAD The requested resource resides temporarily under a different URI.
All 400 level codes * Client Failure
400 Bad Request [HTTP] Any Malformed syntax, for example, empty namespace name in the XML body. [HTTP]
  MKREF User attempted to order a member before or after itself.
  SUBSCRIBE Illegal combination of headers.
  SEARCH No body, invalid scope, etc. The query could not be executed. The request may be malformed (for example, invalid XML). In addition, this can be used for invalid scopes and search redirections.
401 Unauthorized [HTTP] Any Resource requires authorization or authorization was refused [HTTP]
  PROPPATCH Execute a PROPPATCH on two properties, one of which requires authentication to change and the other does not. Result: The entire request will be rejected with a 401.
402 Payment Required [HTTP] Any  
403 Forbidden [HTTP] Any The server understood the request but will not do it. Authorization will not help.
  MKCOL, LOCK, PROPPATCH Client does not have permissions to make a collection, lock the resource, or set a property. [WEBDAV] Check-out attempt: this will be returned if the resource is not versioned or if the resource is a collection.
404 Not Found [HTTP] Any Resource named was not found. [HTTP]
405 Method Not Allowed [HTTP] Any The method was not allowed for the resource named. [HTTP] The response MUST include an Allow header containing a list of valid methods for the requested resource. [HTTP1.1]
  MKCOL This might occur if the resource already exists and thus cannot be created. [WEBDAV]
  MKREF Not an ordered collection.
406 Not Acceptable [HTTP]  Any The resource identified by the request is capable only of generating response entities that have content characteristics that are not acceptable according to the Accept headers sent in the request. The response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. [HTTP1.1]
  HEAD The response need not include an entity as above.
  SUBSCRIBE SUBSCRIBE request had an Accept header that the server could not satisfy.
407 Proxy Authentication Required [HTTP] Any This code is similar to 401 (Unauthorized), but it indicates that the client MUST first authenticate itself with the proxy. [HTTP1.1]
408 Request Timeout [HTTP] Any The client did not produce a request within the time that the server was prepared to wait. [HTTP1.1]
409 Conflict [HTTP] MKCOL A collection cannot be created until intermediate collections have been created. [WEBDAV]
  PROPPATCH The client has provided a value whose semantics are not appropriate for the property, for example, trying to set a read-only property. [WEBDAV]
  PUT Cannot PUT a resource if all ancestors do not already exist. [WEBDAV]

If versioning is being used and the entity being PUT includes changes to a resource that conflict with those made by an earlier (third-party) request, the server might use the 409 response code to indicate that it can't complete the request. [HTTP1.1]

  MKREF Member named for ordering does not exist in the collection.
  SUBSCRIBE Invalid or unsupported notification type.
410 Gone [HTTP] GET The requested resource is no longer available on the server and no forwarding address is known. This condition is considered permanent. [HTTP1.1]
411 Length Required [HTTP] Any The server refuses to accept the request without a defined Content-Length. [HTTP1.1]
412 Precondition Failed [HTTP] Any The precondition given in one or more of the Request header fields evaluated to false when it was tested on the server. [HTTP1.1]
  COPY, MOVE The server was unable to maintain the live-ness of the properties listed in the property behavior XML element, or the overwrite header is F and the state of the destination resource is non-null. [WEBDAV]
  LOCK The lock token could not be enforced or the server could not satisfy the request in the lockinfo XML element.
  SUBSCRIBE, UNSUBSCRIBE The subscription-ID(s) in the header did not match the resource named. This could be because the subscription-ID does not exist any more.
413 Request Entity Too Large [HTTP] Any The server refuses to process a request because the request entity is larger than what the server is willing or able to process. [HTTP1.1]
414 Request URI Too Large [HTTP] Any The server refuses to service the request because the Request-URI is longer than what the server is willing to interpret. [HTTP1.1]
415 Unsupported Media Type [HTTP] Any The server refuses to service the request because the entity of the request is in a format that is not supported by the requested resource for the requested method.
  MKCOL The server does not support the request type of the body. [WEBDAV]
416 Requested Range Not Satisfiable [HTTP1.1]   A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), if none of the range-specifier values in this field overlap with the current extent of the selected resource, and if the request did not include an If-Range request-header field. [HTTP1.1]
417 Expectation Failed [HTTP1.1]   The expectation given in an Expect request-header field (see section 14.20) could not be met by this server or, if the server is a proxy, the server has unambiguous evidence that the next-hop server could not meet the request. [HTTP1.1]
422 Unprocessable Entity [WEBDAV] MKCOL The server understands the content type of the request entity, but was unable to process the instructions that it contains. [WEBDAV] For example, the MKCOL has a request body that is not understood or is incomplete, even if in XML, which is generally accepted in this situation.
  SEARCH Valid XML body in SEARCH, but unsupported or unimplemented query operator.
  LOCK Non-zero depth was specified for a check-out lock, or the Depth header was omitted.
423 Locked [WEBDAV] PROPPATCH, DELETE, MOVE Cannot set properties on, delete, move, or lock a locked resource without the lock token. [WEBDAV]
  LOCK Already locked (need lock token). [WEBDAV] The user tries to create a transaction within a transaction [TRANS].
  COPY The destination resource was locked. [WEBDAV]
424 Method Failure [WEBDAV] PROPPATCH The method was not executed on a resource because some part of the method's execution failed and the whole method was aborted. [WEBDAV]
  UNLOCK One of the methods in the transaction failed, therefore the entire transaction failed.
425 Insufficient Space on Resource SEARCH The query produced more results than the server was willing to transmit. Partial results have been transmitted.
All 500 Level Codes * Server Failure
500 Internal Server Error [HTTP]   The server encountered an unexpected condition that prevented it from fulfilling the request. [HTTP1.1]
501 Not Implemented [HTTP] Any The server does not support the functionality that is required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource. [HTTP1.1]. Contrast with 405.
  PUT Error when a server receives a Content-* header it does not understand in a PUT operation.
  SUBSCRIBE Server does not support the notification method (UDP callback or delivery-control header).
502 Bad Gateway [HTTP]   The server, while acting as a gateway or proxy, received an invalid response from the upstream server that it accessed in attempting to fulfill the request. [HTTP1.1]
  COPY, MOVE The destination could be on another server and the destination server refuses to accept the resource. [WEBDAV]
503 Service Unavailable [HTTP]   The server is currently unable to handle the request due to temporary overloading or to maintenance of the server. The implication is that this is a temporary condition that will be alleviated after a delay. [HTTP1.1]
504 Gateway Timeout   The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (for example, HTTP, FTP, LDAP) or some other auxiliary server (for example, DNS) that it needed to access to complete the request. [HTTP1.1]
505 HTTP Version not supported Any The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. [HTTP1.1]
507 Insufficient Storage PROPPATCH, MKCOL The resource does not have enough space to set the properties or make the collection. [WEBDAV]
  COPY The destination resource does not have sufficient space. [WEBDAV]
  SEARCH The query produced more results than the server was willing to transmit. Partial results have been transmitted. The server MUST send a body that matches the body for code 207, except that there MAY exist resources that matched the search criteria for which no corresponding response exists in the reply.