The Idempotency-Key HTTP Header Field
draft-ietf-httpapi-idempotency-key-header-02
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 | 2023-05-13 (Latest revision 2022-11-09) | ||
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. Discussion Venues This note is to be removed before publishing as an RFC. Discussion of this document takes place on the Building Blocks for HTTP APIs Working Group mailing list (httpapi@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/httpapi/. Source for this draft and an issue tracker can be found at https://github.com/mnot/idempotency.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)