Content Management Interoperability Services (CMIS) Version 1.1

...
5.2.10 Error Handling and Return Codes
HTTP status codes MUST be used to indicate success or failure of an operation. Please see the HTTP
specification for more information on the HTTP status codes. These are provided as guidance from the
HTTP specification. If any conflict arises, the HTTP specification is authoritative.
CMIS Services Exception
General Exceptions
invalidArgument 400
notSupported 405
objectNotFound 404
permissionDenied 403
runtime 500
Specific Exceptions
constraint 409
contentAlreadyExists 409
filterNotValid 400
nameConstraintViolation 409
storage 500
streamNotSupported 403
updateConflict 409
versioning 409
HTTP Status Code
This binding also introduces an object to return additional information about the response. CMIS repositories
SHOULD include this object in responses. When present, the object MUST include the following JSON
properties.
string exception A string containing one of the CMIS services exceptions describe in section 2.2.1.4 Exceptions.
string message A string containing a message that provides more information about what caused the exception.
Example:
GET /cmis/repository/123/myFoldermaxItems=abc HTTP/1.1
Host: www.example.com
User-Agent: Mozilla/5.0
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: xxxx
{
}
"exception": "invalidArgument",
"message": "The parameter 'maxItems' is not valid."
If the query parameter suppressResponseCodes=true is set, the repository MUST always return the
HTTP status code 200.
CMIS-v1.1-csprd01
Standards Track Work Product
Copyright © OASIS Open 2012. All Rights Reserved.
18 August 2012
Page 264 of 331