Sep 30, 2010 · 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 …

Edit conflicts and 409 vs. 412 responses Asked 12 years, 10 months ago Modified 7 years, 1 month ago Viewed 7k times

Jul 22, 2011 · In case the conflict had something to do with the file already existing, I added code to physically delete the file before uploading it, and i'm still getting some 409's.

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...

Jul 27, 2022 · 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 …

Aug 5, 2014 · A 409 Conflict response is definitely wrong if the client can't resolve the conflict and delete the request later. That is, unless the resource has state tracking whether it can be deleted or not, 409 …

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.

Jun 29, 2012 · It's obvious that a successful validation will return a 200 OK. But I don't feel that a success status code is appropriate for a validation failure. I'm leaning towards a 409 Conflict, but I've …

Apr 16, 2020 · 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:

Nov 3, 2020 · 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 …