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/[email protected]/
[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] RIPE Atlas Interface Hackathon, 21-22 May, Copenhagen
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Mon Feb 22 12:10:58 CET 2016
On Mon, Feb 22, 2016 at 12:07:18PM +0100, Jasper den Hertog <jdenhertog at ripe.net> wrote a message of 142 lines which said: > The 'new and standard' way of structuring API requests and output is > here, that I/We am/are trying to adhere to is here: I don't know if it was mentioned at the IETF during the discussion before the approval of draft-ietf-appsawg-http-problem but it is annoying there are two standards... [Insert mandatory xkcd picture on standards.]
- Previous message (by thread): [atlas] Implementing structured error reports ("Problem Details for HTTP APIs")?
- Next message (by thread): [atlas] RIPE Atlas Interface Hackathon, 21-22 May, Copenhagen
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]