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] Confused by the documentation
- Previous message (by thread): [atlas] Confused by the documentation
- Next message (by thread): [atlas] Confused by the documentation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Fri Apr 5 16:33:50 CEST 2024
On Fri, Apr 05, 2024 at 10:13:14AM +0200, Christopher Amin <camin at ripe.net> wrote a message of 44 lines which said: > As a workaround, you can look at the response documentation for "GET > /api/v2/measurements" -- all of the type-specific fields that are > marked with .e.g [http] or [dns] are options which can be included > when creating the measurement. OK, I did not look at the right place. Speaking of these options, what are the possible paths for a HTTP requests at an anchor? I assume the only supported one is "/"?
- Previous message (by thread): [atlas] Confused by the documentation
- Next message (by thread): [atlas] Confused by the documentation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]