This topic created in 5192 days ago, the information mentioned may be changed or developed.
人人的接口发布状态 status_update
{"request_args":[{"value":"1.0","key":"v"},{"value":"fuck","key":"status"},{"value":"status.set","key":"method"},{"value":"JSON","key":"format"},{"value":"177211|6.2b1f19986297cf317185fdd84b3ed365.2592000.1331269200-442","key":"access_token"},{"value":"4a3b8084dd78d20045bcb278022c31be","key":"sig"}],"error_code":8,"error_msg":"服务器繁忙，请稍后再试"}
这个具体会是什么错误？
签名不正确？ 但我用同样的算法获取了用户信息
授权时加了 scope=status_update
{"request_args":[{"value":"1.0","key":"v"},{"value":"fuck","key":"status"},{"value":"status.set","key":"method"},{"value":"JSON","key":"format"},{"value":"177211|6.2b1f19986297cf317185fdd84b3ed365.2592000.1331269200-442","key":"access_token"},{"value":"4a3b8084dd78d20045bcb278022c31be","key":"sig"}],"error_code":8,"error_msg":"服务器繁忙，请稍后再试"}
这个具体会是什么错误？
签名不正确？ 但我用同样的算法获取了用户信息
授权时加了 scope=status_update
 |
1
cloud_dai OP 求解答
|
|
2
cloud_dai OP 找到原因，是access_token的值不对，被截断成长度64，原来是70长的字符串
|
Select Language