Avoid duplicate POSTs with REST

by

Another solution that’s been proposed for this is POST Once Exactly (POE), in which the server generates single-use POST URIs that, when used more than once, will cause the server to return a 405 response.

The downsides are that 1) the POE draft was allowed to expire without any further progress on standardization, and thus 2) implementing it requires changes to clients to make use of the new POE headers, and extra work by servers to implement the POE semantics.

By googling you can find a few APIs that are using it though.

Another idea I had for solving this problem is that of a conditional POST, which I described and asked for feedback on here.

There seems to be no consensus on the best way to prevent duplicate resource creation in cases where the unique URI generation is unable to be PUT on the client and hence POST is needed.

More Related Contents:

  1. RESTful way to create multiple items in one request
  2. Firefox Add-on RESTclient – How to input POST parameters?
  3. What REST PUT/POST/DELETE calls should return by a convention?
  4. RESTful Authentication
  5. RESTful URL design for search
  6. How to post JSON to PHP with curl
  7. What is the proper REST response code for a valid request but an empty data?
  8. HTTP response code for POST when resource already exists
  9. Security of REST authentication schemes
  10. How to make remote REST call inside Node.js? any CURL?
  11. Best practice for partial updates in a RESTful service
  12. Groovy built-in REST/HTTP client?
  13. What is REST? Slightly confused [closed]
  14. Unable to upload zip file through karate framework
  15. API pagination best practices
  16. How to use cURL to send Cookies?
  17. Querystring in REST Resource url
  18. How to construct a REST API that takes an array of id’s for the resources
  19. Spring @ExceptionHandler does not work with @ResponseBody
  20. Best way to support “application/x-www-form-urlencoded” post data with WCF?
  21. Update an entire resource collection in a REST way
  22. What are the best/common RESTful url verbs and actions?
  23. Should I use Singular or Plural name convention for REST resources?
  24. Restful way for deleting a bunch of items
  25. Is it correct to return 404 when a REST resource is not found?
  26. When is it appropriate to respond with a HTTP 412 error?
  27. Swagger documentation with JAX-RS Jersey 2 and Grizzly
  28. How to do a PUT request with cURL?
  29. Maximum default POST request size of IIS 7 – how to increase 64kB/65kB limit?
  30. Get/post to RESTful web service

Leave a Comment