Problem Details for HTTP APIs
draft-nottingham-http-problem-04
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 "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Mark Nottingham , Erik Wilde | ||
| Last updated | 2013-12-05 (Latest revision 2013-06-03) | ||
| Replaced by | draft-ietf-appsawg-http-problem, RFC 7807 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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.)