Failure and verification
05Invalid syntax, unsupported formats, conflicts, and failed preconditions have different responses.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 2.2 ↗
RFC 5789 · § 2.2EXAMPLE
3 / 3
03
Verify uncertain outcome
After a lost response, inspect state rather than blindly replaying a non-idempotent patch.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
400 can indicate malformed patch syntax; 415 an unsupported patch format.
- 400 can indicate malformed patch syntax; 415 an unsupported patch format.
- 409 can indicate a conflict and 412 a failed explicit precondition.
- If a response is lost, GET can help inspect current state; authorize changes and protect their transport.
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