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