2011-10-17 138 views
1

對於谷歌發現,OAuth的頭格式是壞頭響應

GData-Version: 3.0 
Authorization: OAuth oauth_version=1.0,oauth_nonce=5887e5b11904194f7d217e9b7f795d62, oauth_timestamp=1317623602, 
oauth_consumer_key=56565768768.apps.googleusercontent.com",oauth_verifier=PH9etu_6shPOPvlFgiFJS-Dd, 
oauth_token=4%2Fpdn5ZtajHsU-zeSxScNSil43sTK0,oauth_signature_method=HMAC-SHA1, 
oauth_signature=ybgad%2B6LlQ8P3rwnFa8BpI8awok%3D 
Content-Length: 353 
Content-Type: application/atom+xml 

見此做出了Facebook的請求頭爲

Authorization: OAuth oauth_version=1.0,oauth_nonce=5887e5b11904194f7d217e9b7f795d62, oauth_timestamp=1317623602, 
oauth_consumer_key=12904260719,oauth_verifier=PH9etu_6shPOPvlFgiFJS-Dd, 
oauth_token=4%2Fpdn5ZtajHsU-zeSxScNSil43sTK0,oauth_signature_method=HMAC-SHA1, 
oauth_signature=ybgad%2B6LlQ8P3rwnFa8BpI8awok%3D 
Content-Type: application/X-WWW-form-urlencoded 

是什麼在這個頭

錯誤

任何人都可以幫助我請

回答

0

把它解決了。 Facebook不希望包含像oauth_nounce,oauth_consumer_key等參數的頭文件