Client Error Responses Error codes in the 4xx range indicate a client error, such as a malformed request. The service MUST ensure that no observable change has occurred to the state of the service as a result of any request that returns an error status code. In the case that a response body is defined for the error code, the body of the error is as defined for the appropriate . Response Code 404 Not 404 Not Found indicates that the resource specified by the request URL does not exist. The response body MAY provide additional information. Response Code 405 Method Not Allowed 405 Method Not Allowed indicates that the resource specified by the request URL does not support the request method. In this case the response MUST include an Allow header containing a list of valid request methods for the requested resource as specified in [RFC2616]. Response Code 410 Gone 410 Gone indicates that the requested resource is no longer available. This can happen if a client has waited too long to follow a or a link, or a next link on a collection that was requested with. Server Error Responses As specified in [RFC2616], codes in the range indicate service errors. 5xx Response Code 501 Not Implemented If the client requests functionality not implemented by the OData Service, the service MUST respond with 501 Not Implemented and the response body SHOULD describe the functionality not implemented. In-Stream Errors In the case that the service encounters an error after sending a success status to the client, the service MUST generate an error within the payload, which may leave the response malformed. Clients MUST treat the entire response as being in error. This specification does not prescribe a particular format for generating errors within a payload.
Client Error Responses Error codes in the 4xx range indicate a client error, such as a malformed request. The service MUST ensure that no observable change has occurred to the state of the service as a result of any request that returns an error status code. In the case that a response body is defined for the error code, the body of the error is as defined for the appropriate . Response Code 404 Not 404 Not Found indicates that the resource specified by the request URL does not exist. The response body MAY provide additional information. Response Code 405 Method Not Allowed 405 Method Not Allowed indicates that the resource specified by the request URL does not support the request method. In this case the response MUST include an Allow header containing a list of valid request methods for the requested resource as specified in [RFC2616]. Response Code 410 Gone 410 Gone indicates that the requested resource is no longer available. This can happen if a client has waited too long to follow a or a link, or a next link on a collection that was requested with. Server Error Responses As specified in [RFC2616], codes in the 5xx range indicate service errors. Response Code 501 Not Implemented If the client requests functionality not implemented by the OData Service, the service MUST respond with 501 Not Implemented and the response body SHOULD describe the functionality not implemented. In-Stream Errors In the case that the service encounters an error after sending a success status to the client, the service MUST generate an error within the payload, which may leave the response malformed. Clients MUST treat the entire response as being in error. This specification does not prescribe a particular format for generating errors within a payload.
odata-v4.0-wd03-part1-protocol-2013-07-30.docx