curl返回数据大小限制咨询及请求特定URL返回空值问题求助

Hey there! Let's break down why your curl request is returning empty for that second URL, even though it works perfectly in the browser. Let's start with the most likely culprits and work through fixes step by step.

First: Is it a size limit? Short answer—probably not. #

Curl doesn’t have a default size cap on returned data. The CURLOPT_BUFFERSIZE you adjusted is just an internal buffer for optimizing transfer speed, not a limit on how much data you can receive. So that’s not the issue here.

Most Likely Causes & Fixes #

1. Your Timeout is Too Short #

Looking at your code, you set CURLOPT_TIMEOUT,3—that’s a total timeout of 3 seconds. The second request might take longer for the server to process (since it returns more data), and curl is cutting off before getting a full response. Browsers usually have longer default timeouts, which is why it works there.

Fix: Increase the timeout, and split connection vs total timeout for better control, plus add error logging to debug:

public function requestToAvr($url){
 $ch = curl_init();
 curl_setopt($ch, CURLOPT_URL, $url);
 curl_setopt($ch, CURLOPT_HEADER, false);
 curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
 curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
 // Adjust timeouts for slower responses
 curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 5); // Timeout for connecting to the server
 curl_setopt($ch, CURLOPT_TIMEOUT, 10); // Total timeout for the entire request
 $result = curl_exec($ch);
 // Add error checking to pinpoint issues
 if($result === false) {
     error_log('Curl Error: ' . curl_error($ch));
 }
 curl_close($ch);
 return $result;
}

The error log will directly tell you if a timeout is the root cause.

2. URL Special Characters Aren’t Encoded #

Your cmd parameter has curly braces {} and brackets []—browsers automatically URL-encode these characters, but curl might not handle them properly, leading to a malformed request that the server rejects silently.

Fix: URL-encode the cmd value before building the URL:

// Encode the cmd parameter separately to avoid formatting issues
$cmd = "{sid:123,fnc:201,val:[188,24910,5]}";
$url_data = "http://192.168.20.128/?cmd=" . urlencode($cmd);
$ret_data = $this->requestToAvr($url_data);

This ensures all special characters are properly formatted for HTTP requests.

Alternative Function: file_get_contents #

If curl still gives you trouble, you can try file_get_contents (just make sure allow_url_fopen is enabled in your php.ini):

public function requestToAvr($url){
    $context = stream_context_create([
        'http' => [
            'timeout' => 10, // 10-second total timeout
            'header' => "Connection: close\r\n"
        ],
        'ssl' => [
            'verify_peer' => false,
            'verify_name' => false
        ]
    ]);
    $result = file_get_contents($url, false, $context);
    // Debug if the request fails
    if($result === false) {
        error_log('file_get_contents failed for URL: ' . $url);
    }
    return $result;
}

It’s simpler than curl for basic GET requests, though less flexible for complex scenarios like POST requests or custom headers.

Final Debugging Steps #

1. First, add the curl error logging to your existing code—this will tell you exactly why the request is failing (timeout, invalid URL, etc.).
2. Test increasing the timeout first, since that’s the most common issue here.
3. If that doesn’t work, try URL-encoding the cmd parameter to fix formatting issues.

内容的提问来源于stack exchange，提问作者A.A Noman