The Idempotency-Key HTTP Header Field
draft-ietf-httpapi-idempotency-key-header-00
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Jayadeba Jena , Sanjay Dalal | ||
Last updated | 2022-01-02 (Latest revision 2021-07-01) | ||
Replaces | draft-idempotency-header | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The HTTP Idempotency-Key request header field can be used to carry idempotency key in order to make non-idempotent HTTP methods such as "POST" or "PATCH" fault-tolerant.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)