[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 auth status codes on 2 Oct
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Amin
camin at ripe.net
Tue Sep 19 10:44:02 CEST 2023
On 19/09/2023 10:38, Chris Amin wrote: > As a temporary migration measure, the API will keep the same behaviour > (always return 403) if either: > > * The "Referer" header contains "RIPE Atlas Tools" and a version string > <= 3.1.1, or Apologies, this should refer to the "User-Agent" header and not the "Referer" header. > * An "X-Compat" header is set and contains the string "auth-2022" > > This temporary measure is guaranteed to work for the rest of 2022, after > which it will be removed and the API will always make the 401/403 > distinction.
- 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 auth status codes on 2 Oct
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]