qq login api php class_PHP tutorial
Jul 13, 2016 pm 05:49 PM
/**
* QQ operation class
* $Author: shunzi $
* $Id: cls_qq.php 17171 2011-05-30 06:14:00Z shunzi $
*/
class qq_api
{
var $appid = ”;
var $appkey = ”;
var $callback = ”;
var $login_type = 1;
/**
* Constructor
*
* @access public
* @param string $ver version number
*
* @return void
*/
function qq_api($appid, $appkey,$callback,$login_type)
{
$this->appid = $appid;
$this->appkey = $appkey;
$this->callback = $callback;
$this->login_type = $login_type;
}
/**
* @brief Jump to the QQ login page. The request needs to be URL encoded. Please follow RFC 1738
when encoding.
*
* @param $appid
* @param $appkey
* @param $callback
*
* @return The returned string format is: oauth_token=xxx&openid=xxx&oauth_signature=xxx×tamp=xxx&oauth_vericode=xxx
*/
function redirect_to_login()
{
//Jump to the interface address of the QQ login page, do not change it!!
$redirect = “http://openapi.qzone.qq.com/oauth/qzoneoauth_authorize?oauth_consumer_key=”.$this->appid.”&”;
//Call the get_request_token interface to obtain the unauthorized temporary token
$result = array();
$request_token = $this->get_request_token();
parse_str($request_token, $result);
//request token, request token secret need to be saved
//In the demo, save it directly in the global variable.
//In order to avoid the problem of session being unable to be shared caused by multiple subdomains on the website or the same main domain name and different servers
//Developers are requested to make necessary modifications to session.php according to the comments in comm/session.php in this SDK to solve the above two problems,
$_SESSION["token"] = $result["oauth_token"];
$_SESSION["secret"] = $result["oauth_token_secret"];
//print_r($_SESSION);
if ($result["oauth_token"] == "")
{
//Error conditions are not handled in the sample code. In real situations, websites need to handle error situations themselves
exit;
}
////Construct request URL
$redirect .= “oauth_token=".$result["oauth_token"]."&oauth_callback=".rawurlencode($this->callback);
header(“Location:$redirect”);
}
/**
* @brief Requests a temporary token. The request needs to be URL encoded. Please follow RFC 1738
when encoding.
*
* @param $appid
* @param $appkey
*
* @return The returned string format is: oauth_token=xxx&oauth_token_secret=xxx
*/
function get_request_token()
{
//Interface address for requesting temporary token, do not change!!
$url = “http://openapi.qzone.qq.com/oauth/qzoneoauth_request_token?”;
//Generate oauth_signature signature value. For details on how to generate a signature value, see (http://wiki.opensns.qq.com/wiki/[QQ Login] Description of the signature parameter oauth_signature)
//(1) Construct the source string to generate the signature value (HTTP request method & urlencode(uri) & urlencode(a=x&b=y&…))
$sigstr = “GET”.”&”.rawurlencode(“http://openapi.qzone.qq.com/oauth/qzoneoauth_request_token”).”&”;
//Required parameters
$params = array();
$params["oauth_version"] = “1.0″;
$params["oauth_signature_method"] = “HMAC-SHA1″;
$params["oauth_timestamp"] = time();
$params["oauth_nonce"] = mt_rand();
$params["oauth_consumer_key"] = $this->appid;
//Serialize the parameters in ascending alphabetical order
$normalized_str = $this->get_normalized_string($params);
$sigstr .= rawurlencode($normalized_str);
//(2) Construct key
$key = $this->appkey.”&”;
//(3) Generate oauth_signature signature value. Here you need to ensure that the PHP version supports the hash_hmac function
$signature = $this->get_signature($sigstr, $key);
//Construct request url
$url?.= $normalized_str.”&”.”oauth_signature=”.rawurlencode($signature);
//echo “$sigstrn”;
//echo “$urln”;
return file_get_contents($url);
}
/*
* @brief Get user information. The request needs to be URL encoded. Please follow RFC 1738
when encoding.
*
* @param $appid
* @param $appkey
* @param $access_token
* @param $access_token_secret
* @param $openid
*
*/
function get_user_info($access_token, $access_token_secret, $openid)
{
//Interface address for obtaining user information, do not change!!
$url = “http://openapi.qzone.qq.com/user/get_user_info”;
$info = $this->do_get($url, $access_token, $access_token_secret, $openid);
$arr = array();
$arr = json_decode($info, true);
return $arr;
}
/**
* @brief Get access_token. The request needs to be URL encoded. Please follow RFC 1738
when encoding.
*
* @param $appid
* @param $appkey
* @param $request_token
* @param $request_token_secret
* @param $vericode
*
* @return The returned string format is: oauth_token=xxx&oauth_token_secret=xxx&openid=xxx&oauth_signature=xxx&oauth_vericode=xxx×tamp=xxx
*/
function get_access_token($request_token, $request_token_secret, $vericode)
{
//Request the interface address of access_token with Qzone access permission, do not change!!
$url = “http://openapi.qzone.qq.com/oauth/qzoneoauth_access_token?”;
//Generate oauth_signature signature value. For details on how to generate a signature value, see (http://wiki.opensns.qq.com/wiki/[QQ Login] Description of the signature parameter oauth_signature)
//(1) Construct the source string to generate the signature value (HTTP request method & urlencode(uri) & urlencode(a=x&b=y&…))
$sigstr = “GET”.”&”.rawurlencode(“http://openapi.qzone.qq.com/oauth/qzoneoauth_access_token”).”&”;
//Necessary parameters, do not change them casually!!
$params = array();
$params["oauth_version"] = “1.0″;
$params["oauth_signature_method"] = “HMAC-SHA1″;
$params["oauth_timestamp"] = time();
$params["oauth_nonce"] = mt_rand();
$params["oauth_consumer_key"] = $this->appid;
$params["oauth_token"] = $request_token;
$params["oauth_vericode"] = $vericode;
//Serialize the parameters in ascending alphabetical order
$normalized_str = $this->get_normalized_string($params);
$sigstr .= rawurlencode($normalized_str);
//echo “sigstr = $sigstr”;
//(2) Construct key
$key = $this->appkey.”&”.$request_token_secret;
//(3) Generate oauth_signature signature value. Here you need to ensure that the PHP version supports the hash_hmac function
$signature = $this->get_signature($sigstr, $key);
//Construct request url
$url?.= $normalized_str.”&”.”oauth_signature=”.rawurlencode($signature);
return file_get_contents($url);
}
/**
* @brief Sort parameters in ascending dictionary order
*
* @param $params parameter list
*
* @return key-value pairs linked with & after sorting (key1=value1&key2=value2…)
*/
function get_normalized_string($params)
{
ksort($params);
$normalized = array();
foreach($params as $key => $val)
{
$normalized[] = $key.”=”.$val;
}
return implode(“&”, $normalized);
}
/**
* @brief Use HMAC-SHA1 algorithm to generate oauth_signature signature value
*
* @param $key Key
* @param $str source string
*
* @return signature value
*/
function get_signature($str, $key)
{
$signature = “”;
if (function_exists(‘hash_hmac’))
{
$signature = base64_encode(hash_hmac(“sha1″, $str, $key, true));
}
else
{
$blocksize = 64;
$hashfunc = ‘sha1′;
if (strlen($key) > $blocksize)
{
$key = pack(‘H*’, $hashfunc($key));
}
$key = str_pad($key,$blocksize,chr(0×00));
$ipad = str_repeat(chr(0×36),$blocksize);
$opad = str_repeat(chr(0x5c),$blocksize);
$hmac = pack(
‘H*’,$hashfunc(
($key^$opad).pack(
‘H*’,$hashfunc(
($key^$ipad).$str
)
)
)
);
$signature = base64_encode($hmac);
}
return $signature;
}
/**
* @brief URL-encodes the string, following rfc1738 urlencode
*
* @param $params
*
* @return URL-encoded string
*/
function get_urlencode_string($params)
{
ksort($params);
$normalized = array();
foreach($params as $key => $val)
{
$normalized[] = $key.”=”.rawurlencode($val);
}
return implode(“&”, $normalized);
}
/**
* @brief Check if openid is legal
*
* @param $openid corresponds to the user’s QQ number
* @param $timestamp Timestamp
* @param $sig Signature value
*
* @return true or false
*/
function is_valid_openid($openid, $timestamp, $sig)
{
$key = $this->appkey;
$str = $openid.$timestamp;
$signature = $this->get_signature($str, $key);
//echo “sig:$sign”;
//echo “str:$strn”;
return $sig == $signature;
}
/**
* @brief All Get requests can use this method
*
* @param $url
* @param $appid
* @param $appkey
* @param $access_token
* @param $access_token_secret
* @param $openid
*
* @return true or false
*/
function do_get($url, $access_token, $access_token_secret, $openid)
{
$sigstr = “GET”.”&”.rawurlencode(“$url”).”&”;
//必要參數(shù), 不要隨便更改!!
$params = $_GET;
$params["oauth_version"]????????? = “1.0″;
$params["oauth_signature_method"] = “HMAC-SHA1″;
$params["oauth_timestamp"]??????? = time();
$params["oauth_nonce"]??????????? = mt_rand();
$params["oauth_consumer_key"]???? = $this->appid;
$params["oauth_token"]??????????? = $access_token;
$params["openid"]???????????????? = $openid;
unset($params["oauth_signature"]);
//參數(shù)按照字母升序做序列化
$normalized_str = $this->get_normalized_string($params);
$sigstr??????? .= rawurlencode($normalized_str);
//簽名,確保php版本支持hash_hmac函數(shù)
$key = $this->appkey.”&”.$access_token_secret;
$signature = $this->get_signature($sigstr, $key);
$url????? .= “?”.$normalized_str.”&”.”oauth_signature=”.rawurlencode($signature);
//echo “$urln”;
return file_get_contents($url);
}
/**
* @brief All multi-part post requests can use this method
*
* @param $url
* @param $appid
* @param $appkey
* @param $access_token
* @param $access_token_secret
* @param $openid
*
*/
function do_multi_post($url, $appid, $appkey, $access_token, $access_token_secret, $openid)
{
//構(gòu)造簽名串.源串:方法[GET|POST]&uri&參數(shù)按照字母升序排列
$sigstr = “POST”.”&”.”$url”.”&”;
//必要參數(shù),不要隨便更改!!
$params = $_POST;
$params["oauth_version"]????????? = “1.0″;
$params["oauth_signature_method"] = “HMAC-SHA1″;
$params["oauth_timestamp"]??????? = time();
$params["oauth_nonce"]??????????? = mt_rand();
$params["oauth_consumer_key"]???? = $appid;
$params["oauth_token"]??????????? = $access_token;
$params["openid"]???????????????? = $openid;
unset($params["oauth_signature"]);
//獲取上傳圖片信息
foreach ($_FILES as $filename => $filevalue)
{
if ($filevalue["error"] != UPLOAD_ERR_OK)
{
//echo “upload file error $filevalue['error']n”;
//exit;
}
$params[$filename] = file_get_contents($filevalue["tmp_name"]);
}
//對(duì)參數(shù)按照字母升序做序列化
$sigstr .= $this->get_normalized_string($params);
//簽名,需要確保php版本支持hash_hmac函數(shù)
$key = $appkey.”&”.$access_token_secret;
$signature = $this->get_signature($sigstr, $key);
$params["oauth_signature"] = $signature;
//處理上傳圖片
foreach ($_FILES as $filename => $filevalue)
{
$tmpfile = dirname($filevalue["tmp_name"])."/".$filevalue["name"];
move_uploaded_file($filevalue["tmp_name"], $tmpfile);
$params[$filename] = “@$tmpfile”;
}
/*
echo “l(fā)en: “.strlen($sigstr).”n”;
echo “sig: $sigstrn”;
echo “key: $appkey&n”;
*/
$ch = curl_init();
curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
curl_setopt($ch, CURLOPT_POST, TRUE);
curl_setopt($ch, CURLOPT_POSTFIELDS, $params);
curl_setopt($ch, CURLOPT_URL, $url);
$ret = curl_exec($ch);
//$httpinfo = curl_getinfo($ch);
//print_r($httpinfo);
curl_close($ch);
//Delete upload temporary files
unlink($tmpfile);
return $ret;
}
/**
* @brief All post requests can use this method
*
* @param $url
* @param $appid
* @param $appkey
* @param $access_token
* @param $access_token_secret
* @param $openid
*
*/
function do_post($url, $appid, $appkey, $access_token, $access_token_secret, $openid)
{
//Construct signature string. Source string: method [GET|POST]&uri& parameters are arranged in ascending alphabetical order
$sigstr = “POST”.”&”.rawurlencode($url).”&”;
//Necessary parameters, do not change them casually!!
$params = $_POST;
$params["oauth_version"] = “1.0″;
$params["oauth_signature_method"] = “HMAC-SHA1″;
$params["oauth_timestamp"] = time();
$params["oauth_nonce"] = mt_rand();
$params["oauth_consumer_key"] = $appid;
$params["oauth_token"] = $access_token;
$params["openid"]???????= $openid;
unset($params["oauth_signature"]);
//Serialize the parameters in ascending alphabetical order
$sigstr .= rawurlencode($this->get_normalized_string($params));
//Signature, you need to ensure that the php version supports the hash_hmac function
$key = $appkey.”&”.$access_token_secret;
$signature = $this->get_signature($sigstr, $key);
$params["oauth_signature"] = $signature;
$postdata = $this->get_urlencode_string($params);
//echo “$sigstr******n”;
//echo “$postdatan”;
$ch = curl_init();
curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
curl_setopt($ch, CURLOPT_POST, TRUE);
curl_setopt($ch, CURLOPT_POSTFIELDS, $postdata);
curl_setopt($ch, CURLOPT_URL, $url);
$ret = curl_exec($ch);
curl_close($ch);
return $ret;
}
}
?>
Currently there is only login function, the method will continue to be updated in later projects
Excerpted from Shunzi Network PHP website construction

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

User voice input is captured and sent to the PHP backend through the MediaRecorder API of the front-end JavaScript; 2. PHP saves the audio as a temporary file and calls STTAPI (such as Google or Baidu voice recognition) to convert it into text; 3. PHP sends the text to an AI service (such as OpenAIGPT) to obtain intelligent reply; 4. PHP then calls TTSAPI (such as Baidu or Google voice synthesis) to convert the reply to a voice file; 5. PHP streams the voice file back to the front-end to play, completing interaction. The entire process is dominated by PHP to ensure seamless connection between all links.

The core method of building social sharing functions in PHP is to dynamically generate sharing links that meet the requirements of each platform. 1. First get the current page or specified URL and article information; 2. Use urlencode to encode the parameters; 3. Splice and generate sharing links according to the protocols of each platform; 4. Display links on the front end for users to click and share; 5. Dynamically generate OG tags on the page to optimize sharing content display; 6. Be sure to escape user input to prevent XSS attacks. This method does not require complex authentication, has low maintenance costs, and is suitable for most content sharing needs.

To realize text error correction and syntax optimization with AI, you need to follow the following steps: 1. Select a suitable AI model or API, such as Baidu, Tencent API or open source NLP library; 2. Call the API through PHP's curl or Guzzle and process the return results; 3. Display error correction information in the application and allow users to choose whether to adopt it; 4. Use php-l and PHP_CodeSniffer for syntax detection and code optimization; 5. Continuously collect feedback and update the model or rules to improve the effect. When choosing AIAPI, focus on evaluating accuracy, response speed, price and support for PHP. Code optimization should follow PSR specifications, use cache reasonably, avoid circular queries, review code regularly, and use X

1. Maximizing the commercial value of the comment system requires combining native advertising precise delivery, user paid value-added services (such as uploading pictures, top-up comments), influence incentive mechanism based on comment quality, and compliance anonymous data insight monetization; 2. The audit strategy should adopt a combination of pre-audit dynamic keyword filtering and user reporting mechanisms, supplemented by comment quality rating to achieve content hierarchical exposure; 3. Anti-brushing requires the construction of multi-layer defense: reCAPTCHAv3 sensorless verification, Honeypot honeypot field recognition robot, IP and timestamp frequency limit prevents watering, and content pattern recognition marks suspicious comments, and continuously iterate to deal with attacks.

PHP does not directly perform AI image processing, but integrates through APIs, because it is good at web development rather than computing-intensive tasks. API integration can achieve professional division of labor, reduce costs, and improve efficiency; 2. Integrating key technologies include using Guzzle or cURL to send HTTP requests, JSON data encoding and decoding, API key security authentication, asynchronous queue processing time-consuming tasks, robust error handling and retry mechanism, image storage and display; 3. Common challenges include API cost out of control, uncontrollable generation results, poor user experience, security risks and difficult data management. The response strategies are setting user quotas and caches, providing propt guidance and multi-picture selection, asynchronous notifications and progress prompts, key environment variable storage and content audit, and cloud storage.

PHP ensures inventory deduction atomicity through database transactions and FORUPDATE row locks to prevent high concurrent overselling; 2. Multi-platform inventory consistency depends on centralized management and event-driven synchronization, combining API/Webhook notifications and message queues to ensure reliable data transmission; 3. The alarm mechanism should set low inventory, zero/negative inventory, unsalable sales, replenishment cycles and abnormal fluctuations strategies in different scenarios, and select DingTalk, SMS or Email Responsible Persons according to the urgency, and the alarm information must be complete and clear to achieve business adaptation and rapid response.

PHPisstillrelevantinmodernenterpriseenvironments.1.ModernPHP(7.xand8.x)offersperformancegains,stricttyping,JITcompilation,andmodernsyntax,makingitsuitableforlarge-scaleapplications.2.PHPintegrateseffectivelyinhybridarchitectures,servingasanAPIgateway

The core role of Homebrew in the construction of Mac environment is to simplify software installation and management. 1. Homebrew automatically handles dependencies and encapsulates complex compilation and installation processes into simple commands; 2. Provides a unified software package ecosystem to ensure the standardization of software installation location and configuration; 3. Integrates service management functions, and can easily start and stop services through brewservices; 4. Convenient software upgrade and maintenance, and improves system security and functionality.
