Problem Details for HTTP APIs
draft-nottingham-http-problem-07
| Document | Type |
Replaced Internet-Draft
(appsawg WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mark Nottingham , Erik Wilde | ||
| Last updated | 2014-07-27 | ||
| Replaced by | draft-ietf-appsawg-http-problem | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-appsawg-http-problem | |
| 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
This document defines a "problem detail" as a way to carry machine- readable details of errors in a HTTP response, to avoid the need to invent new error response formats for HTTP APIs. Note to Readers This draft should be discussed on the apps-discuss mailing list [1].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)