Thanks Denis, I did notice this way of supplying passwords in the API documentation, but I have no idea what password I am supposed to supply or where that password will originate from..? This is prabably bleeding obvious to someone with any domain knowledge, which unfortunately I don't possess yet. Regards, Roger Kind Kristiansen On 09/16/2011 04:56 PM, Denis Walker wrote:
Dear Roger Kind Kristiansen,
I am assuming your question is "how to get the required password 'into the update engine' to perform updates?"
Passwords are sent as HTTP parameters, for example
https://lab.db.ripe.net/whois/modify/<source>/<object-type>/<primary-key>?password=...
regards Denis Walker Business Analyst RIPE NCC Database Group
On 16/09/11:38 3:58 PM, Roger Kristiansen wrote:
The first part of this question can be disregarded, as I got confirmation that the server is indeed down ATM.
Still wondering about the password, though, so.. anyone? :-)
Regards, Roger Kind Kristiansen
On 09/16/2011 03:16 PM, Roger Kristiansen wrote:
Hi,
First of all: I'm not sure if this is the correct mailing list for questions regarding the Database REST API. If it isn't then I'm sorry, and I hope you might point me in the right direction.
I am in need of API access to the RIPE database, both for querying and updating. I have been looking at the REST API documented at http://labs.ripe.net/ripe-database/database-api/api-documentation.
I can connect, but I am unable to get a response from the lab.db.ripe.net server. No error or anything else. I'm accessing the server from the address 193.69.55.146.
Here's one example, using curl on one of your example URLs:
$ curl -v http://lab.db.ripe.net/whois/lookup/ripe/mntner/RIPE-DBM-MNT * About to connect() to lab.db.ripe.net port 80 (#0) * Trying 193.0.19.31... connected * Connected to lab.db.ripe.net (193.0.19.31) port 80 (#0)
GET /whois/lookup/ripe/mntner/RIPE-DBM-MNT HTTP/1.1 User-Agent: curl/7.21.3 (i686-pc-linux-gnu) libcurl/7.21.3 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 Host: lab.db.ripe.net Accept: */*
.. then nothing. Anyone know what might be wrong here?
Also I'm not quite sure where or how to get the required password to perform updates. Any pointers? Would be much appreciated. :-)
Regards, Roger Kind Kristiansen