Conditional PATCH
03A strong ETag precondition prevents applying a base-dependent patch to the wrong version.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 2 ↗
RFC 5789 · § 2EXAMPLE
3 / 3
03
Reject stale patch
The client retrieves current state instead of silently corrupting it.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Clients should use a conditional request when the patch depends on a known base.
- Clients should use a conditional request when the patch depends on a known base.
- If-Match can protect against collisions between concurrent edits.
- Some patch formats are designed for idempotence; the method alone does not guarantee it.
Examples are illustrative. Consult the linked RFC and its errata for implementation details.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy