coap
CoAP Response Codes
Response codes returned by CoAP (Constrained Application Protocol) servers, as defined in RFC 7252 and related IoT specifications.
27 codes
· All codes 27 codes
- 2.01 Created The request succeeded and a new resource was created. Sent in response to POST and PUT requests, analogous to HTTP 201 Created.
- 2.02 Deleted The request succeeded and the resource was deleted, or did not exist in the first place. Sent in response to DELETE requests.
- 2.03 Valid The response to a conditional GET request confirms the client's cached representation is still current, analogous to HTTP 304 Not Modified.
- 2.04 Changed The request succeeded and the resource was updated. Sent in response to POST and PUT requests when no new resource is created.
- 2.05 Content The request succeeded and the response payload contains the requested representation. Sent in response to GET requests, analogous to HTTP 200 OK.
- 2.31 Continue An intermediate block in a block-wise transfer was accepted; the client should send the next block.
- 4.00 Bad Request The server could not understand the request due to malformed syntax, analogous to HTTP 400 Bad Request.
- 4.01 Unauthorized The client is not authorized to access the requested resource, analogous to HTTP 401 Unauthorized.
- 4.02 Bad Option The request contained an unrecognized critical option that the server was unable to process.
- 4.03 Forbidden The server understood the request but refuses to authorize it, analogous to HTTP 403 Forbidden.
- 4.04 Not Found The server does not have a resource matching the request URI, analogous to HTTP 404 Not Found.
- 4.05 Method Not Allowed The method specified in the request is not valid for the target resource, analogous to HTTP 405 Method Not Allowed.
- 4.06 Not Acceptable The resource identified by the request cannot generate a representation matching the Accept options in the request.
- 4.08 Request Entity Incomplete The server has not received all blocks of a block-wise request body that it needs to proceed.
- 4.09 Conflict The modification requested by a PATCH or iPATCH request would leave the resource in an inconsistent state that the server cannot resolve.
- 4.12 Precondition Failed One or more conditions given in the request header options evaluated to false, analogous to HTTP 412 Precondition Failed.
- 4.13 Request Entity Too Large The server refuses to process the request because the request payload is larger than it is willing or able to handle.
- 4.15 Unsupported Content-Format The Content-Format of the request payload is not supported by the server for the requested method or resource.
- 4.22 Unprocessable Entity The server understood the content type and syntax of a PATCH or FETCH request but was unable to process the contained instructions.
- 4.29 Too Many Requests The client has sent too many requests in a given time and the server is rate-limiting it, analogous to HTTP 429 Too Many Requests.
- 5.00 Internal Server Error The server encountered an unexpected condition that prevented it from fulfilling the request, analogous to HTTP 500 Internal Server Error.
- 5.01 Not Implemented The server does not support the functionality required to fulfill the request, analogous to HTTP 501 Not Implemented.
- 5.02 Bad Gateway The server, acting as a gateway or proxy, received an invalid response from an upstream server it accessed to fulfill the request.
- 5.03 Service Unavailable The server is currently unable to handle the request due to temporary overloading or maintenance, analogous to HTTP 503 Service Unavailable.
- 5.04 Gateway Timeout The server, acting as a gateway or proxy, did not receive a timely response from an upstream server it accessed to fulfill the request.
- 5.05 Proxying Not Supported The server is configured as a forward-proxy but does not support forwarding the request to the specified target.
- 5.08 Hop Limit Reached A forward-proxy sent the request onward, but the request's Hop-Limit option reached zero before delivery, indicating a likely proxy loop.