Problem Details for HTTP APIs
draft-ietf-appsawg-http-problem-00
The information below is for an old version of the document.
| Document | Type | Expired Internet-Draft (appsawg WG) | |
|---|---|---|---|
| Authors | Mark Nottingham , Erik Wilde | ||
| Last updated | 2015-03-23 (Latest revision 2014-09-19) | ||
| Replaces | draft-nottingham-http-problem | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Reviews |
GENART Last Call review
(of
-01)
Ready with Issues
|
||
| Stream | WG state | WG Consensus: Waiting for Write-Up | |
| Document shepherd | Alexey Melnikov | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | "Alexey Melnikov" <alexey.melnikov@isode.com> |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-ietf-appsawg-http-problem-00.txt
https://www.ietf.org/archive/id/draft-ietf-appsawg-http-problem-00.txt
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.)