[db-wg] Getting: HTTP/1.1 401 UNAUTHORIZED
- Previous message (by thread): [db-wg] Getting: HTTP/1.1 401 UNAUTHORIZED
- Next message (by thread): [db-wg] Blocking Access to Personal Data Objects in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Thu May 22 08:34:22 CEST 2014
Hello, On 2014.05.21. 22:21, Ye, Hong wrote: > Hi Gurus, > > I am new to RIPE API and hope someone can help me get through this. > > Could some please let me know what is the proper way to use “curl” to get > data back from following URL? > I could use the same login name/password get in web portal but not from > command line. Do I have to encode > my logins? Or should I pass my logins as part of the URL parameters? > > Regards > > Hong Ye > > https://atlas.ripe.net/api/v1/measurement/xxxxxxxxxxx/result/?start=1392336000&stop=1392249599&format=json ... >> GET > /api/v1/measurement/xxxxxxxxxxx/result/?start=1392336000&stop=1392249599&format=json > HTTP/1.1 ... > < HTTP/1.1 401 UNAUTHORIZED ... The most likely reason for this is that the measurement is not marked as public; in that case we insist on authenticating the user. You can solve this in two ways: 1. mark the measurement public (you can edit its settings if you created it) 2. use API keys -- see https://atlas.ripe.net/docs/keys/ for details Note: this is somewhat off-topic for this list. I recommend using the RIPE Atlas mailing list (ripe-atlas at ripe.net) or the MAT-WG list (mat-wg at ripe.net) for Atlas related questions. Regards, Robert Kisteleki
- Previous message (by thread): [db-wg] Getting: HTTP/1.1 401 UNAUTHORIZED
- Next message (by thread): [db-wg] Blocking Access to Personal Data Objects in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]