|
- HTTP response code for POST when resource already exists
So why is 409 Conflict the most appropriate status code in a situation described in the OP's question? RFC 7231 describes 409 Conflict status code as follows: 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
- Excel Number Format: What is [$-409]? - Stack Overflow
The Workbook must be unshared to do this To delete the Format [$-409] identified above under the "Normal" cell type from the workbook, Right click on a cell, select Custom, scroll until you find the [$-409] format type identified above, delete then all formats will return back to what is called general
- Return an object along with a 409 Conflict error in a Web API 2 POST . . .
Arrived here looking for help with ASP NET Core HTTP 409 - this is related, just the newer approach to solving this same problem Conflict ActionResult return Conflict(new { message = $"An existing record with the id '{id}' was already found "});
- REST HTTP status code if DELETE impossible - Stack Overflow
I'd say 409 is the most appropriate, given it's wording in the RFC: 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 The server SHOULD
- Reasons for a 409 Conflict HTTP error when uploading a file to . . .
I encountered similar issue when uploading a file returned 409 Besides issues mentioned above it can also happen due to file size restrictions for POST on the server side For example, tomcat (java web server) have POST size limit of 2MB by default
- Is returning HTTP 409 appropriate for a validation check?
409 is another situation where the data are valid and processed, but the action was rejected In this case, we are wanting to know if it is safe to proceed I'd probably prefer to perform the desired action, and then return errors if it could not be completed, but it is necessary to indicate after changes leading up to the 'final' action if we
- Newest http-status-code-409 Questions - Stack Overflow
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
- 422 or 409 status code for existing email during signup
409 is a Conflict for PUT, like 2 requests concurrently update same entity, one succeeds, another 409 because ETag has been updated Some frameworks libs server might emit 409 automatically, for that reason I'd prefer 422 - there is a guaranty no one except my code emit it, so monitoring tool reports won't be false positive (because 409 is
|
|
|