RFC 5789: PATCH Method for HTTP
In plain English — editorial summary, not part of the RFC
Several applications extending the Hypertext Transfer Protocol (HTTP) require a feature to do partial resource modification. The existing HTTP PUT method only allows a complete replacement of a document. This proposal adds a new HTTP method, PATCH, to modify an existing HTTP resource. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5789
- Published
- March 2010
- Authors
- L. Dusseault; J. Snell
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5843Additional Hash Algorithms for HTTP Instance DigestsCurrent
April 2010
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 6331Moving DIGEST-MD5 to HistoricCurrent
July 2011
- RFC 7231Hypertext Transfer Protocol (HTTP/1.1): Semantics and ContentObsoleted
June 2014
- RFC 7232Hypertext Transfer Protocol (HTTP/1.1): Conditional RequestsObsoleted
June 2014
- RFC 7234Hypertext Transfer Protocol (HTTP/1.1): CachingObsoleted
June 2014
- RFC 7235Hypertext Transfer Protocol (HTTP/1.1): AuthenticationObsoleted
June 2014
- RFC 7236Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme RegistrationsCurrent
June 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?