[p3t] Structured error messages and RFC 7807

[Dave Morris]

Apparently RFC7807 has been replaced by RFC9457, which is almost but not 
quite the same.

https://blog.frankel.ch/problem-details-http-apis/

https://datatracker.ietf.org/doc/html/rfc9457

-- Dave


On 2024-10-24 02:05, Russ Allbery via p3t wrote:
> I keep forgetting that this standard exists, so since structured error
> messages came up in the call today and I happened to remember it while
> editing some other documents, I wanted to send out a link before I 
> forgot
> it again.
> 
> https://datatracker.ietf.org/doc/html/rfc7807
> 
> is an existing standard for structured HTTP error messages that 
> predefines
> a JSON type and a set of standard fields.  It's extensible in that any
> implementation is allowed to add new fields that don't conflict with 
> the
> standard fields.  The IVOA could define one or more problem types (in 
> the
> language of this standard) for our structured error message, which 
> would
> mean any client that understood RFC 7807 application/problem+json 
> errors
> would automatically be aware of at least the standard fields.
> 
> --
> Russ Allbery (eagle at eyrie.org)             
> <https://www.eyrie.org/~eagle/>