This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Implementing structured error reports ("Problem Details for HTTP APIs")?
- Previous message (by thread): [atlas] Implementing structured error reports ("Problem Details for HTTP APIs")?
- Next message (by thread): [atlas] Implementing structured error reports ("Problem Details for HTTP APIs")?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Mon Feb 22 12:03:18 CET 2016
On 2016-02-22 11:08, Stephane Bortzmeyer wrote:
> Hello,
>
> IETF approved the future RFC draft-ietf-appsawg-http-problem "Problem
> Details for HTTP APIs" which standardize structured error reports (in
> JSON) to add machine-readable information to HTTP error codes.
>
> Would it be a good idea to convert current Atlas reports
> ({"error":{"status":400,"code":104,"detail":"__all__: Your selected
> prefix is not covered by our network.","title":"Bad Request"}}) to the
> new and standard format?
Thanks for the heads up! We'll look at this, most likely when it actually
becomes an RFC :)
Regards,
Robert
- Previous message (by thread): [atlas] Implementing structured error reports ("Problem Details for HTTP APIs")?
- Next message (by thread): [atlas] Implementing structured error reports ("Problem Details for HTTP APIs")?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]