The third part of our series was about If-Match and how you can use it to prevent lost updates for PUT and PATCH - two clients process the same resource, the server detects the collision based on the ETag and rejects the stale write access. One question remained unanswered: What about POST? When …