Patch versus replacement
01PATCH submits modification instructions rather than a complete replacement representation.
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
Apply the specified change
Other values survive according to the patch format.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Complete replacement with PUTRFC 5789 §1
This document adds PATCH for partial modification because PUT replacement does not express a generic set of modification instructions. JSON Patch is specified separately.
Read the updated RFC section ↗The request media type identifies the patch-document format.
- The request media type identifies the patch-document format.
- PATCH is neither safe nor inherently idempotent.
- Creation of a missing target is possible only when the patch format and permissions allow 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