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] Changes to RIPE Atlas API auth status codes on 2 Oct
- Previous message (by thread): [atlas] Changes to RIPE Atlas API auth status codes on 2 Oct
- Next message (by thread): [atlas] Changes to RIPE Atlas API keys
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Amin
camin at ripe.net
Tue Sep 19 11:15:29 CEST 2023
On 19/09/2023 11:11, Gert Doering wrote: >> This temporary measure is guaranteed to work for the rest of 2022, > > So which iteration of 2022 would that be? Thanks Gert. This was of course deliberate to make see whether people were paying attention. The temporary measure is *also* guaranteed to work for the rest of 2023, and the X-Compat header may contain either "auth-2022" or "auth-2023" to maintain the old behaviour until the end of this year. Chris
- Previous message (by thread): [atlas] Changes to RIPE Atlas API auth status codes on 2 Oct
- Next message (by thread): [atlas] Changes to RIPE Atlas API keys
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]