twitter oAuth cURL示例不起作用-为什么?
可能重复:twitter oAuth cURL示例不起作用-为什么?,curl,twitter,oauth,Curl,Twitter,Oauth,可能重复: 下面的代码简单地告诉了我: 验证oauth签名和令牌失败 // Set url $url = "http://api.twitter.com/oauth/request_token"; // Params to pass to twitter and create signature $params['oauth_callback'] = "http://localhost/twitter/tweet/";
下面的代码简单地告诉了我: 验证oauth签名和令牌失败
// Set url
$url = "http://api.twitter.com/oauth/request_token";
// Params to pass to twitter and create signature
$params['oauth_callback'] = "http://localhost/twitter/tweet/";
$params['oauth_consumer_key'] = $this->consumerKey;
$params['oauth_nonce'] = SHA1(time());
$params['oauth_timestamp'] = time();
$params['oauth_signature_method'] = $this->signatureMethod;
$params['oauth_version'] = $this->version;
ksort($params);
// Signing
// Concatenating
$concatenatedParams = '';
foreach($params as $k => $v)
{
$k = urlencode($k);
$v = urlencode($v);
$concatenatedParams .= "{$k}={$v}&";
}
$concatenatedParams = urlencode(substr($concatenatedParams,0,-1));
$signatureBaseString = "POST&".urlencode($url)."&".$concatenatedParams;
$base64Hashmac = base64_encode( hash_hmac('sha1', $signatureBaseString, $this->secret."&", true) );
$params['oauth_signature'] = urlencode($base64Hashmac);
// Do cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLINFO_HEADER_OUT, 1);
curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $params);
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER,1);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION,1);
$exec = curl_exec ($ch);
$info = curl_getinfo($ch);
curl_close ($ch);
print $exec;
下面是从curls$info打印出来的信息
Array
(
[url] => http://api.twitter.com/oauth/request_token
[content_type] => text/html; charset=utf-8
[http_code] => 401
[header_size] => 919
[request_size] => 181
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 1.176
[namelookup_time] => 0
[connect_time] => 0.127
[pretransfer_time] => 0.127
[size_upload] => 934
[size_download] => 44
[speed_download] => 37
[speed_upload] => 794
[download_content_length] => 44
[upload_content_length] => 934
[starttransfer_time] => 0.127
[redirect_time] => 0
[request_header] => POST /oauth/request_token HTTP/1.1
Host: api.twitter.com
Accept: */*
Content-Length: 934
Content-Type: multipart/form-data; boundary=----------------------------7465678a46cc
)
您可能想要确切地说明它是如何工作的,事情可能会以许多不同的方式“不工作”。您是否得到错误结果?它们是什么,来自哪些电话?有哪一步失败了吗 首先,您不能使用“localhost”地址作为回调URL,如果twitter服务器连接到“localhost”,它将只连接到自身,而不是您
另外,您构建
$concatenatedParams
的方式只对$signatureBaseString
进行了部分URL编码。不要使用“{$k}%3D{$v}%26”
而是正常使用=
和&
,然后urlencode
将最后完成的$concatedparams
添加到$signatureBaseString$concatedparams.=“{$k}%3D{$v}%26”;应该完成url编码,但我尝试了一下,还是失败了。我按照您的建议更新了代码->但不是运气嘿。经过base64编码后,哈希\u hmac在分配给oauth\u签名
参数之前也必须进行url编码,我不知道这是否发生在base64\u encode
内部。不是这样,而是已经更新了。运气不好,同样的错误。您可能希望尝试使用GET并将oauth参数作为Authorization:header发送,这是Twitter网站上推荐的: