HTTP response code for POST when resource already exists This is going to be a pretty long answer, the short summary of which is that HTTP 409 is the most appropriate status code to report the failure of an "add new resource" operation, in case a resource with the same identifier already exists What follows is the explanation why, based solely on what's stated in the authoritative source - RFC 7231
Excel Number Format: What is [$-409]? - Stack Overflow The [$-409] is a locale code, given in hexadecimal Prefixing a date with a certain locale code determines what is shown when you use the various date time format codes
rest - What to return with a 409 conflict? - Stack Overflow If the user is already registered by that email, I'll return a 409 CONFLICT status However, I'm not quite sure what the proper content is required to return with that -- for example, do I return that user object?
Publish to Azure web app sub application fails with 409 error Error: Conflict (CODE: 409) ##[debug]Processed: ##vso[task complete result=Failed;]Error: Failed to create path 'site wwwroot api' from Kudu Error: Conflict (CODE: 409) When manually trying to add the "api" folder to the azure web app, I also get an error: The deployment task to deploy the api looks like this:
Distinguishing HTTP status code 403 and 409 in practice (or 400) Even after reading many documents, books, spec I couldn't 100% be certain whether I should use http status code 403 or 409 in my case Some argue that 403 should be used only with an authorization
REST HTTP status code if DELETE impossible - Stack Overflow The 409 (Conflict) status code indicates that the request could not be completed due to a conflict with the current state of the target resource This code is used in situations where the user might be able to resolve the conflict and resubmit the request
Is it OK to use a 409 HTTP code in the case when the record with . . . 409 is a fine choice for your case - in particular, it calls attention to the body of the request, informs that there is some incompatibility between the semantics of the current request and the current state of the resource, and indicates that the client may be able to resolve the conflict and resubmit the request