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] Invalid JSON because of DNS TXT records
- Previous message (by thread): [atlas] New on RIPE Labs: AMS-IX Outage during RIPE70 as Seen with RIPE Atlas
- Next message (by thread): [atlas] Invalid JSON because of DNS TXT records
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Fri May 15 06:50:41 CEST 2015
The DNS, as we know, is a jungle. People put anything in their TXT records, even control characters. Atlas faithfully returns this content in the JSON files (see measurement #2004707). Then they are no longer legal JSON (RFC 7159, section 7) and crash the JSON libraries. Who should fix it? My first guess is that Atlas should not produce illegal JSON files and therefore should escape such texts.
- Previous message (by thread): [atlas] New on RIPE Labs: AMS-IX Outage during RIPE70 as Seen with RIPE Atlas
- Next message (by thread): [atlas] Invalid JSON because of DNS TXT records
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]