Problem Details for HTTP APIs
draft-ietf-httpapi-rfc7807bis-01
| Document | Type | Expired Internet-Draft (httpapi WG) | |
|---|---|---|---|
| Authors | Mark Nottingham , Erik Wilde , Sanjay Dalal | ||
| Last updated | 2022-04-16 (Latest revision 2021-10-13) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-ietf-httpapi-rfc7807bis-01.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 define new error response formats for HTTP APIs. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at https://github.com/ietf-wg-httpapi/rfc7807bis.
Authors
Mark Nottingham
Erik Wilde
Sanjay Dalal
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)