HTTP status code for update and delete

Question

What status code should I set for UPDATE  PUT  and DELETE  e g  product successfully updated

User · Answer

Here s some status code  which you should know for your kind of knowledge   1XX Information Responses        100 Continue   101 Switching Protocols   102 Processing   103 Early Hints      2XX Success        200 OK   201 Created   202 Accepted   203 Non-Authoritative Information   204 No Content   205 Reset Content   206 Partial Content   207 Multi-Status   208 Already Reported   226 IM Used      3XX Redirection        300 Multiple Choices   301 Moved Permanently   302 Found   303 See Other   304 Not Modified   305 Use Proxy   306 Switch Proxy   307 Temporary Redirect   308 Permanent Redirect      4XX Client errors        400 Bad Request   401 Unauthorized   402 Payment Required   403 Forbidden   404 Not Found   405 Method Not Allowed   406 Not Acceptable   407 Proxy Authentication Required   408 Request Timeout   409 Conflict   410 Gone   411 Length Required   412 Precondition Failed   413 Payload Too Large   414 URI Too Long   415 Unsupported Media Type   416 Range Not Satisfiable   417 Expectation Failed   418 I m a teapot   420 Method Failure   421 Misdirected Request   422 Unprocessable Entity   423 Locked   424 Failed Dependency   426 Upgrade Required   428 Precondition Required   429 Too Many Requests   431 Request Header Fields Too Large   451 Unavailable For Legal Reasons      5XX Server errors        500 Internal Server error   501 Not Implemented   502 Bad Gateway   503 Service Unavailable   504 gateway Timeout   505 Http version not supported   506 Varient Also negotiate   507 Insufficient Storage   508 Loop Detected   510 Not Extended   511 Network Authentication Required

User · Answer

Since the question delves into if DELETE  should  return 200 vs 204 it is worth considering that some people recommend returning an entity with links so the preference is for 200       Instead of returning 204  No Content   the API should be helpful and   suggest places to go  In this example I think one obvious link to   provide is to   somewhere com container    minus  resource    - the container from which   the client just deleted a resource  Perhaps the client wishes to   delete more resources  so that would be a helpful link     http   blog ploeh dk 2013 04 30 rest-lesson-learned-avoid-204-responses      If a client encounters a 204 response  it can either give up  go to   the entry point of the API  or go back to the previous resource it   visited  Neither option is particularly good    Personally I would not say 204 is wrong  neither does the author  he says  annoying   because good caching at the client side has many benefits  Best is to be consistent either way

User · Answer

Here are some Tips  DELETE   200  if you want send some additional data in the Response  or 204  recommended    202 Operation deleted has not been committed yet   If there s nothing to delete  use 204 or 404  DELETE operation is idempotent  delete an already deleted item is operation successful  so you can return 204  but it s true that idempotent doesn t necessarily imply the same response    Other errors   400 Bad Request  Malformed syntax or a bad query is strange but possible   401 Unauthorized Authentication failure 403 Forbidden  Authorization failure or invalid Application ID  405 Not Allowed  Sure  409 Resource Conflict can be possible in complex systems  And 501  502 in case of errors    PUT  If you re updating an element of a collection  200 204 with the same reasons as DELETE above  202 if the operation has not been commited yet   The referenced element doesn t exists   PUT can be 201  if you created the element because that is your behaviour   404 If you don t want to create elements via PUT   400 Bad Request  Malformed syntax or a bad query more common than in case of DELETE    401 Unauthorized  403 Forbidden  Authentication failure or invalid Application ID   405 Not Allowed  Sure   409 Resource Conflict can be possible in complex systems  as in DELETE   422 Unprocessable entity It helps to distinguish between a  quot Bad request quot   e g  malformed XML JSON  and invalid field values  And 501  502 in case of errors

User · Answer

quot VALIDATON ERROR quot              quot code quot   512           quot message quot    quot Validation error quot              quot CONTINUE quot              quot code quot   100           quot message quot    quot Continue quot              quot SWITCHING PROTOCOLS quot              quot code quot   101           quot message quot    quot Switching Protocols quot              quot PROCESSING quot              quot code quot   102           quot message quot    quot Processing quot              quot OK quot              quot code quot   200           quot message quot    quot OK quot              quot CREATED quot              quot code quot   201           quot message quot    quot Created quot              quot ACCEPTED quot              quot code quot   202           quot message quot    quot Accepted quot              quot NON AUTHORITATIVE INFORMATION quot              quot code quot   203           quot message quot    quot Non Authoritative Information quot              quot NO CONTENT quot              quot code quot   204           quot message quot    quot No Content quot              quot RESET CONTENT quot              quot code quot   205           quot message quot    quot Reset Content quot              quot PARTIAL CONTENT quot              quot code quot   206           quot message quot    quot Partial Content quot              quot MULTI STATUS quot              quot code quot   207           quot message quot    quot Multi-Status quot              quot MULTIPLE CHOICES quot              quot code quot   300           quot message quot    quot Multiple Choices quot              quot MOVED PERMANENTLY quot              quot code quot   301           quot message quot    quot Moved Permanently quot              quot MOVED TEMPORARILY quot              quot code quot   302           quot message quot    quot Moved Temporarily quot              quot SEE OTHER quot              quot code quot   303           quot message quot    quot See Other quot              quot NOT MODIFIED quot              quot code quot   304           quot message quot    quot Not Modified quot              quot USE PROXY quot              quot code quot   305           quot message quot    quot Use Proxy quot              quot TEMPORARY REDIRECT quot              quot code quot   307           quot message quot    quot Temporary Redirect quot              quot PERMANENT REDIRECT quot              quot code quot   308           quot message quot    quot Permanent Redirect quot              quot BAD REQUEST quot              quot code quot   400           quot message quot    quot Bad Request quot              quot UNAUTHORIZED quot              quot code quot   401           quot message quot    quot Unauthorized quot              quot PAYMENT REQUIRED quot              quot code quot   402           quot message quot    quot Payment Required quot              quot FORBIDDEN quot              quot code quot   403           quot message quot    quot Forbidden quot              quot NOT FOUND quot              quot code quot   404           quot message quot    quot Not Found quot              quot METHOD NOT ALLOWED quot              quot code quot   405           quot message quot    quot Method Not Allowed quot              quot NOT ACCEPTABLE quot              quot code quot   406           quot message quot    quot Not Acceptable quot              quot PROXY AUTHENTICATION REQUIRED quot              quot code quot   407           quot message quot    quot Proxy Authentication Required quot              quot REQUEST TIMEOUT quot              quot code quot   408           quot message quot    quot Request Timeout quot              quot CONFLICT quot              quot code quot   409           quot message quot    quot Conflict quot              quot GONE quot              quot code quot   410           quot message quot    quot Gone quot              quot LENGTH REQUIRED quot              quot code quot   411           quot message quot    quot Length Required quot              quot PRECONDITION FAILED quot              quot code quot   412           quot message quot    quot Precondition Failed quot              quot REQUEST TOO LONG quot              quot code quot   413           quot message quot    quot Request Entity Too Large quot              quot REQUEST URI TOO LONG quot              quot code quot   414           quot message quot    quot Request-URI Too Long quot              quot UNSUPPORTED MEDIA TYPE quot              quot code quot   415           quot message quot    quot Unsupported Media Type quot              quot REQUESTED RANGE NOT SATISFIABLE quot              quot code quot   416           quot message quot    quot Requested Range Not Satisfiable quot              quot EXPECTATION FAILED quot              quot code quot   417           quot message quot    quot Expectation Failed quot              quot IM A TEAPOT quot              quot code quot   418           quot message quot    quot I m a teapot quot              quot INSUFFICIENT SPACE ON RESOURCE quot              quot code quot   419           quot message quot    quot Insufficient Space on Resource quot              quot METHOD FAILURE quot              quot code quot   420           quot message quot    quot Method Failure quot              quot UNPROCESSABLE ENTITY quot              quot code quot   422           quot message quot    quot Unprocessable Entity quot              quot LOCKED quot              quot code quot   423           quot message quot    quot Locked quot              quot FAILED DEPENDENCY quot              quot code quot   424           quot message quot    quot Failed Dependency quot              quot PRECONDITION REQUIRED quot              quot code quot   428           quot message quot    quot Precondition Required quot              quot TOO MANY REQUESTS quot              quot code quot   429           quot message quot    quot Too Many Requests quot              quot REQUEST HEADER FIELDS TOO LARGE quot              quot code quot   431           quot message quot    quot Request Header Fields Too quot              quot UNAVAILABLE FOR LEGAL REASONS quot              quot code quot   451           quot message quot    quot Unavailable For Legal Reasons quot              quot INTERNAL SERVER ERROR quot              quot code quot   500           quot message quot    quot Internal Server Error quot              quot NOT IMPLEMENTED quot              quot code quot   501           quot message quot    quot Not Implemented quot              quot BAD GATEWAY quot              quot code quot   502           quot message quot    quot Bad Gateway quot              quot SERVICE UNAVAILABLE quot              quot code quot   503           quot message quot    quot Service Unavailable quot              quot GATEWAY TIMEOUT quot              quot code quot   504           quot message quot    quot Gateway Timeout quot              quot HTTP VERSION NOT SUPPORTED quot              quot code quot   505           quot message quot    quot HTTP Version Not Supported quot              quot INSUFFICIENT STORAGE quot              quot code quot   507           quot message quot    quot Insufficient Storage quot              quot NETWORK AUTHENTICATION REQUIRED quot              quot code quot   511           quot message quot    quot Network Authentication Required quot

User · Answer

RFC 2616 describes which status codes to use   And no  it s not always 200

User · Answer

In addition to 200 and 204  205  Reset Content  could be a valid response      The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent      e g   clearing of the form in which the input is given

User · Answer

Short answer  for both PUT and DELETE  you should send either 200  OK  or 204  No Content     Long answer  here s a complete decision diagram  click to magnify      Source  https   github com for-GET http-decision-diagram

User · Answer

In June 2014 RFC7231 obsoletes RFC2616  If you are doing REST over HTTP then RFC7231 describes exactly what behaviour is expected from GET  PUT  POST and DELETE

User · Answer

For a PUT request  HTTP 200 or HTTP 204 should imply  quot resource updated successfully quot   For a DELETE request  HTTP 200 or HTTP 204 should imply  quot resource deleted successfully quot   HTTP 202 can also be returned which would imply that the instruction was accepted by the server and the  quot resource was marked for deletion quot    PUT If an existing resource is modified  either the 200  OK  or 204  No Content  response codes SHOULD be sent to indicate successful completion of the request    DELETE A successful response SHOULD be 200  OK  if the response includes an entity describing the status  202  Accepted  if the action has not yet been enacted  or 204  No Content  if the action has been enacted but the response does not include an entity   Source  W3 org  HTTP 1 1 Method Definitions  HTTP 200 OK  Standard response for successful HTTP requests  The actual response will depend on the request method used  HTTP 204 No Content  The server successfully processed the request  but is not returning any content  Source  List of HTTP status codes  2xx Success

[http] HTTP status code for update and delete?

1XX Information Responses

2XX Success

3XX Redirection

4XX Client errors

5XX Server errors

Examples related to http

Examples related to http-status-codes

Examples related to http-status-code-415