I got this from https://dev.twitter.com/apps/2037768/oauth (the on line API tool) application kegare.modernmarianas.com (my test & development site)
It failed when I ran it from my command line. Any hints? Or do I misunderstand how the online OAuth tool is to be used?
Jim
(AKA Be_Elzebub)
curl --request ‘POST’ ‘https://api.twitter.com/oauth/request_token’ --header ‘Authorization: OAuth oauth_consumer_key=“8lbQNod5tl0IGy43L7OWQg”, oauth_nonce=“2f4855e1c94e36363e0c89aad4a8bd1d”, oauth_signature=“AarlSI65skVNyFPblMDVlz2%2FO9k%3D”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1335147203”, oauth_token=“26007638-SLnKBVCqiBFt4EjPTTpacC8txIAAFNZKHTFqsTuJ9”, oauth_version=“1.0”’ --verbose
This is what it did:
$curl --request ‘POST’ ‘https://api.twitter.com/oauth/request_token’ --header ‘Authorization: OAuth oauth_consumer_key=“8lbQNod5tl0IGy43L7OWQg”, oauth_nonce=“2f4855e1c94e36363e0c89aad4a8bd1d”, oauth_signature=“AarlSI65skVNyFPblMDVlz2%2FO9k%3D”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1335147203”, oauth_token=“26007638-SLnKBVCqiBFt4EjPTTpacC8txIAAFNZKHTFqsTuJ9”, oauth_version=“1.0”’ --verbose
- About to connect() to api.twitter.com port 443 (#0)
- Trying 199.59.148.20… connected
- Connected to api.twitter.com (199.59.148.20) port 443 (#0)
- SSLv3, TLS handshake, Client hello (1):
- SSLv3, TLS handshake, Server hello (2):
- SSLv3, TLS handshake, CERT (11):
- SSLv3, TLS handshake, Server finished (14):
- SSLv3, TLS handshake, Client key exchange (16):
- SSLv3, TLS change cipher, Client hello (1):
- SSLv3, TLS handshake, Finished (20):
- SSLv3, TLS change cipher, Client hello (1):
- SSLv3, TLS handshake, Finished (20):
- SSL connection using RC4-SHA
- Server certificate:
- subject: C=US; ST=California; L=San Francisco; O=Twitter, Inc.; OU=Twitter Platform; CN=api.twitter.com
- start date: 2010-05-18 00:00:00 GMT
- expire date: 2012-05-17 23:59:59 GMT
- common name: api.twitter.com (matched)
- issuer: C=US; O=VeriSign, Inc.; OU=VeriSign Trust Network; OU=Terms of use at https://www.verisign.com/rpa ©09; CN=VeriSign Class 3 Secure Server CA - G2
- SSL certificate verify ok.
POST /oauth/request_token HTTP/1.1
User-Agent: curl/7.21.4 (universal-apple-darwin11.0) libcurl/7.21.4 OpenSSL/0.9.8r zlib/1.2.5
Host: api.twitter.com
Accept: /
Authorization: OAuth oauth_consumer_key=“8lbQNod5tl0IGy43L7OWQg”, oauth_nonce=“2f4855e1c94e36363e0c89aad4a8bd1d”, oauth_signature=“AarlSI65skVNyFPblMDVlz2%2FO9k%3D”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1335147203”, oauth_token=“26007638-SLnKBVCqiBFt4EjPTTpacC8txIAAFNZKHTFqsTuJ9”, oauth_version=“1.0”
< HTTP/1.1 401 Unauthorized
< Date: Mon, 23 Apr 2012 02:16:27 GMT
< Status: 401 Unauthorized
< Last-Modified: Mon, 23 Apr 2012 02:16:27 GMT
< X-Frame-Options: SAMEORIGIN
< X-MID: 62ece0dc92cd4b4c36c521b7a9c9169211b83cc9
< X-Runtime: 0.01224
< Content-Type: text/html; charset=utf-8
< Content-Length: 44
< X-Transaction: a8a49717039a1605
< Expires: Tue, 31 Mar 1981 05:00:00 GMT
< Pragma: no-cache
< Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
< Vary: Accept-Encoding
< Server: tfe
<
- Connection #0 to host api.twitter.com left intact
- Closing connection #0
- SSLv3, TLS alert, Client hello (1):
Failed to validate oauth signature and token
