If-Match ETag Precondition vs Body Version Validation for Confluence REST Write Retries
When an integration retries a Confluence REST write after a timeout, the goal is to avoid creating duplicate pages or applying the same version increment twice. Two documented optimistic concurrency controls address this constraint with different failure modes. The first uses ETag headers returned on content resources. A retry sends the captured ETag in an I