Problem Details for HTTP APIs
RFC 9457
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2023-12-15
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2023-12-14
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2023-08-02
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document defines a "problem detail" to carry machine-readable details of errors in HTTP response content … Received changes through RFC Editor sync (changed abstract to '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.') |
|
2023-08-01
|
(System) | IANA registries were updated to include RFC9457 |
|
2023-07-31
|
(System) | Received changes through RFC Editor sync (created alias RFC 9457, changed abstract to 'This document defines a "problem detail" to carry machine-readable details of … Received changes through RFC Editor sync (created alias RFC 9457, changed abstract to '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.', changed pages to 16, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-07-31, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-httpapi-rfc7807bis and RFC 7807) |
|
2023-07-31
|
(System) | RFC published |