Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
While RFC2626 suggests only PUT requests to return 409, this can also be useful for POST requests.
The text was updated successfully, but these errors were encountered:
+1. We use POSTs to update resources, but sometimes the edits don't make sense, so it would be useful to return a 409 after executing post!.
Sorry, something went wrong.
If the edits don't make sense, then 422 unprocessable entity might be a better choice.
+1. I've got basically the exact same problem as in this post: https://groups.google.com/forum/#!msg/clojure-liberator/iaxFQPMZqJs/bMETIFMLHwwJ - the email address in our user table must be unique, and a 409 should be returned for a POST to create a user with an email address that already exists in the table.
+1, similar use case as @rlinehan's
+1, also similar to @rlinehan's
I'm open for a PR. I suggest to support conflict for POST to move the decision "conflict?" be before "post-to-existing?" (see the graph for reference: http://clojure-liberator.github.io/liberator/assets/img/decision-graph.svg). After that change conflict? will be called for POST and PUT requests.
No branches or pull requests