RFC 9457: Problem Details for HTTP APIs
In plain English — editorial summary, not part of the RFC
This document defines a "problem detail" to carry machine-readable details of errors in HTTP response content to avoid the need to define new error response formats for HTTP APIs. This document obsoletes RFC 7807.
Document record
- Document ID
- RFC9457
- Published
- July 2023
- Authors
- M. Nottingham; E. Wilde; S. Dalal
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 16
- Also known as
- —
- Obsoletes:
- RFC 7807
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9264Linkset: Media Types and a Link Relation Type for Link SetsCurrent
July 2022
- RFC 8631Link Relation Types for Web ServicesCurrent
July 2019
- RFC 7396JSON Merge PatchCurrent
October 2014
- RFC 7386JSON Merge PatchObsoleted
October 2014
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 4826Extensible Markup Language (XML) Formats for Representing Resource ListsCurrent
May 2007
- RFC 4825The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)Current
May 2007
- RFC 9440Client-Cert HTTP Header FieldCurrent
July 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?