[atlas] Implementing structured error reports ("Problem Details for HTTP APIs")?
- Previous message (by thread): [atlas] Thirteen new RIPE Atlas anchors have joined the community
- Next message (by thread): [atlas] Implementing structured error reports ("Problem Details for HTTP APIs")?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Mon Feb 22 11:08:20 CET 2016
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?
- Previous message (by thread): [atlas] Thirteen new RIPE Atlas anchors have joined the community
- Next message (by thread): [atlas] Implementing structured error reports ("Problem Details for HTTP APIs")?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]