you're "updating" it to the same data that's already there
or not, when someone else already changed it.
you're "updating" it to the same data that's already there
or not, when someone else already changed it.
I would standardize an RPOST (for reliable post) method which would either accept a message ID from the client or return a new URI with a message ID in it.
The answer!
we need to make certain that we set up our system so that multiple POSTs of the same data are not harmful
This is the goal of this article.
not cacheable, unless the response includes appropriate Cache-Control or Expires header fields
To read more about Cache-Control header see: https://tools.ietf.org/html/rfc7234#section-5.2
If a server responds to a POST or other non-idempotent request with a 303 See Other response and a value for the location header, the client is expected to obtain the resource mentioned in the location header using the GET method