You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2020. It is now read-only.
Shouldn't PUT requests be for updating key/value pairs within a document, and POST for overwriting/creating a document? PUT behaves the same as POST in this instance.
The text was updated successfully, but these errors were encountered:
PUT is idempotent by nature. If you want to use PUT to update a resource, it must be a full resource update; you MUST send all attribute values in a PUT request to guarantee idempotency.
POSTting TWICE to /accounts SHOULD create two accounts.
PUTting to /accounts SHOULD fail (nothing to update).
POSTting TWICE to /accounts/jnovack SHOULD result in 1 account with exactly the same data (perhaps, save for last-modified).
PUTting TWICE to /accounts/jnovack SHOULD result in 1 account with exactly the same data (perhaps, save for last-modified).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Shouldn't PUT requests be for updating key/value pairs within a document, and POST for overwriting/creating a document? PUT behaves the same as POST in this instance.
The text was updated successfully, but these errors were encountered: