English
English
When using PHP for network requests, we often encounter situations where we need to simulate browser behavior, especially the verification problem of verification codes. Verification codes are techniques used to prevent automated programs from submitting forms. They usually require users to enter a displayed character or click on a specific picture to verify human identity. In this case, using the cURL library to simulate browser behavior is an effective solution.
cURL is a powerful PHP library that can help us send HTTP requests to external servers, and supports multiple protocols such as HTTP, HTTPS, FTP, etc. For requests that need to be processed for verification code verification, the key is how to manage and cache cookies to be reused across multiple requests. At this time, we can use the curl_share_init function to implement shared cookies, thereby solving the problem of frequent verification of verification codes.
curl_share_init is a function provided by cURL to initialize a handle to a shared resource. It is usually used to share cookies, DNS and other information between multiple cURL requests. This function allows multiple cURL requests to share the same cookie, which is useful for scenarios where the same site needs to be requested multiple times and remain logged in or authenticated.
By sharing cookies, we can avoid re-geting verification codes every time we request it. This can more effectively simulate browser behavior and avoid frequent verification code verification.
Here is a simple example that demonstrates how to use the curl_share_init function to cache cookies and share them over multiple requests.
<?php
// Initialize a shared handle
$ch_share = curl_share_init();
// Initialize the first one cURL ask
$ch1 = curl_init();
curl_setopt($ch1, CURLOPT_URL, "https://m66.net/login"); // Replace with the URL you need to visit
curl_setopt($ch1, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch1, CURLOPT_COOKIEJAR, "cookies.txt"); // keep Cookie Go to the file
curl_setopt($ch1, CURLOPT_SHARE, $ch_share); // shared Cookie
$response1 = curl_exec($ch1);
// Submit after analog input verification code
$ch2 = curl_init();
curl_setopt($ch2, CURLOPT_URL, "https://m66.net/submit_form"); // Replace with the URL where the form needs to be submitted
curl_setopt($ch2, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch2, CURLOPT_POST, true);
curl_setopt($ch2, CURLOPT_POSTFIELDS, [
'username' => 'testuser',
'password' => 'testpassword',
'captcha' => 'captcha_code' // Assuming the verification code has been entered
]);
curl_setopt($ch2, CURLOPT_SHARE, $ch_share); // shared Cookie
$response2 = curl_exec($ch2);
// closure cURL ask
curl_close($ch1);
curl_close($ch2);
// closureshared句柄
curl_share_close($ch_share);
// 输出ask结果
echo "Response from first request: " . $response1;
echo "Response from second request: " . $response2;
?>
Initialize a shared handle : Use curl_share_init to initialize a shared handle $ch_share , which will be used to share cookies, DNS, and other settings between multiple cURL requests.
First request : In the first cURL request, we use curl_setopt to set the URL, return content, and COOKIEJAR parameters, indicating that the cookies are saved to the cookies.txt file. This request will request the verification code page locally, simulating the first access process.
Second request : In the second request, we submit a form with the username, password and verification code. By setting the CURLOPT_SHARE parameter to the shared handle $ch_share , this allows the second request to reuse the cookies in the first request, thus avoiding duplicate verification code verification.
Close resource : After the request is completed, we use curl_close to close each cURL session, and finally use curl_share_close to close the shared handle.
Avoid duplicate verification code verification : By sharing cookies, we can reuse the same login status and authentication information in multiple requests, avoiding re-entering the verification code every time we request.
Improve efficiency : If each request needs to re-acquire the verification code, it will not only affect the user experience, but also increase the time for network requests. Using shared cookies can significantly improve the efficiency of requests.
Limitations of shared resources : While curl_share_init can help us share resources in multiple requests, make sure not to use the same shared handles in too many concurrent requests, as this may lead to competition and exceptions of resources.
Using curl_share_init to share cURL requested cookies is an effective way to solve verification code verification problems. When multiple requests are required, by caching and sharing cookies, duplicate verification code input can be avoided and operational efficiency can be improved. Whether it is login verification or submitting forms, the cURL sharing mechanism can help us better simulate browser behavior and reduce interference caused by verification code.
