Hi,
You can find this in the documentation at:
https://atlas.ripe.net/docs/howtos/anchors.html#http-s
Cheers,
Robert
On Fri, Apr 5, 2024 at 4:33 PM Stephane Bortzmeyer wrote:
>
> On Fri, Apr 05, 2024 at 10:13:14AM +0200,
> Christopher Amin wrote
> a message of 44 lines which said:
>
> > As
On Fri, Apr 05, 2024 at 10:13:14AM +0200,
Christopher Amin 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
On Fri, Apr 05, 2024 at 01:53:02PM +0200,
Robert Kisteleki wrote
a message of 36 lines which said:
> Thank you for pointing this out, it has been fixed: the anchors
> respond with a proper 404 now.
Indeed, thanks.
--
ripe-atlas mailing list
ripe-atlas@ripe.net
Dear Stephane,
Thank you for pointing this out, it has been fixed: the anchors
respond with a proper 404 now.
Regards,
Robert, reporting for the people who fixed it
On Thu, Apr 4, 2024 at 6:48 PM Stephane Bortzmeyer wrote:
>
> It seems the anchors, when receiving a HTTP request for a
Dear colleagues,
On Wednesday 10 April we will carry out maintenance on a storage
solution used by critical backend nodes of the Atlas infrastructure.
Work start: 2024-04-10 08:00 UTC
Work end: 2024-04-1011:00 UTC
What you should expect during the maintenance window:
- The LIR
Hi Stéphane,
You're right, the REST API reference for "POST api/v2/measurements"
doesn't document the valid options that can be included when creating
a measurement. This is a regression that we will fix.
As a workaround, you can look at the response documentation for "GET
/api/v2/measurements"
