Request failed successfully
Re:Developers don't understand CORS (2019)
by locknitpicker on Sunday June 21, 2026 @03:04PM
(#48621637)
It's the graphql way.
Re:Developers don't understand CORS (2019)
by gbuk2013 on Tuesday June 23, 2026 @03:48AM
(#48641683)
Not really, more like succeed without having to do anything.
The key is the perspective of what success is: it’s the state where the resource does not exist, or is the action having deleted the resource. But 200/202 is perfectly capable of expressing the distinction in the latter case as well.
> Then you'd return 202 on a request to delete any invalid element, which really doesn't sound right
It depends on your use-case if you care about this or not. If you do care you will have to handle it either way somehow.
But if you want an idempotent API then a success is more appropriate IMO than an error.
Then you'd return 202 on a request to delete any invalid element, which really doesn't sound right.
> 200 with some sort of response to distinguish (e.g. { changed: boolean }).
Sounds even worse, and much like APIs that returns 200 with a payload saying {error:"not found"}