RESTful Reponse Code

IBM
REST API response codes and error messages
https://www.ibm.com/support/knowledgecenter/SSQP76_8.8.0/com.ibm.odm.dserver.events.ref/topics/ref_dse_restapi_responsecodes_errormsgs.html

－－－－－－－－－

REST API Tutorial
HTTP Status Codes
https://restfulapi.net/http-status-codes/

－－－－－－－－－

REST API Tutorial
HTTP Status Codes
https://www.restapitutorial.com/httpstatuscodes.html

－－－－－－－－－
－－－－－－－－－

Java EE 7 Tutorial
P.29-9
If no methods in a resouce are able to produce the MIME type in a client request, the JAX-RS runtime sends back an HTTP "406 Not Acceptable" error.

－－－－－－－－－

406 NOT ACCEPTABLE     The data format requested in the Accept header or accept parameter is not supported by the targeted resource. That is, the client has requested that data is returned in a particular format, but the server is unable to return data in that format.

－－－－－－－－－

MDN web docs
Accept
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept

－－－－－－－－－
－－－－－－－－－

Java EE 7 Tutorial
P.29-10
If a resouce is unable to consume the MIME type of a client request, the JAX-RS runtime sends back an HTTP 415 ("Unsupported Media Type") error.

－－－－－－－－－

415 UNSUPPORTED MEDIA TYPE     The data format of the request body, specified in the Content-Type header, is unsupported by the targeted resource.

－－－－－－－－－

MDN web docs
Content-Type
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type

－－－－－－－－－
－－－－－－－－－

Java EE 7 Tutorial
P.29-11
Note that the resouce method returns void. This means that no representation is returned and that a response with a status code of HTTP 204 ("No Content") will be returned.

－－－－－－－－－

204 NO CONTENT Indicates that the request was accepted but that there was nothing to return. This is returned when the request was processed, but no additional information about the result has been returned.

－－－－－－－－－
－－－－－－－－－

Java EE 7 Tutorial
P.29-12
If the step value cannot be parsed as a 32-bit signed integer, an HTTP 400 ("Client Error") response is returned.

－－－－－－－－－

400 BAD REQUEST The request was not valid. This code is returned when the server has attempted to process the request, but some aspect of the request is not valid, for example an incorrectly formatted resource or an attempt to deploy an invalid event project to the event runtime. Information about the request is provided in the response body, and includes an error code and error message.