Search:

Search all manuals
Search this manual
Manual
Couchbase Server Manual 2.0
Community Wiki and Resources
Download Couchbase Server 2.0
Couchbase Developer Guide 2.0
Client Libraries
Couchbase Server Forum
Additional Resources
Community Wiki
Community Forums
Couchbase SDKs
Parent Section
8 Using the REST API
Chapter Sections
Chapters

8.3. HTTP Status Codes

The Couchbase Server will return one of the following HTTP status codes in response to your REST API request:

Table 8.2. REST API — HTTP Status Codes

HTTP StatusDescription
200 OKSuccessful request and an HTTP response body returns. If this creates a new resource with a URI, the 200 status will also have a location header containing the canonical URI for the newly created resource.
201 CreatedRequest to create a new resource is successful, but no HTTP response body returns. The URI for the newly created resource returns with the status code.
202 AcceptedThe request is accepted for processing, but processing is not complete. Per HTTP/1.1, the response, if any, SHOULD include an indication of the request's current status, and either a pointer to a status monitor or some estimate of when the request will be fulfilled.
204 No ContentThe server fulfilled the request, but does not need to return a response body.
400 Bad RequestThe request could not be processed because it contains missing or invalid information, such as validation error on an input field, a missing required value, and so on.
401 UnauthorizedThe credentials provided with this request are missing or invalid.
403 ForbiddenThe server recognized the given credentials, but you do not possess proper access to perform this request.
404 Not FoundURI you provided in a request does not exist.
405 Method Not AllowedThe HTTP verb specified in the request (DELETE, GET, HEAD, POST, PUT) is not supported for this URI.
406 Not AcceptableThe resource identified by this request cannot create a response corresponding to one of the media types in the Accept header of the request.
409 ConflictA create or update request could not be completed, because it would cause a conflict in the current state of the resources supported by the server. For example, an attempt to create a new resource with a unique identifier already assigned to some existing resource.
500 Internal Server ErrorThe server encountered an unexpected condition which prevented it from fulfilling the request.
501 Not ImplementedThe server does not currently support the functionality required to fulfill the request.
503 Service UnavailableThe server is currently unable to handle the request due to temporary overloading or maintenance of the server.