|
- 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
- formatting - My Excel row is locked at height of 409. 5 and I want to . . .
Create a row below the row you want taller than 409 5 Select cell of top row, and cell of bottom row Click arrow next to the Merge Center button in the Alignment section of the Home tab on the ribbon Click Merge Cells You can repeat this process multiple times if two cells worth of height isn't enough
- 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
- REST HTTP status code if DELETE impossible - Stack Overflow
409 (Conflict) : Seems appropriate but the client should have the possibility to resolve the conflict with the API but that's not the case here Update : The data binding that prevents the resource to be deleted cannot be changed via the REST API However the resource can be "freed" via other way as the database from which the data comes from
- 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
- 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
- Edit conflicts and 409 vs. 412 responses - Stack Overflow
The problem here is that it mandates using a timestamp and also the spec says you MUST return 412 We'd like to return more specific 409 code, to indicate it is an edit conflict, as described in the spec, instead of much more generic 412 which can be caused by other reasons This would also make it much easier for the client to have special
- 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
|
|
|