Question 226199 in CentOS Question posted in
The official documentation can be found here.

Centos – PHP script CURL string returns no result for long string (612300 chars) works if string below 500k characters

I’m hoping someone can help me debug this issue, I have a PHP script that works fine gathering a single string of encrypted data, up until the string returned is above around 500,000 characters.

My script currently is outputting at 612,300 characters, at this point the CURL returns an empty result.

If however I lower the string to below 500,000 characters, CURL can display the data in the result.

Does anyone know why this is, and how I could go about allowing an unlimited return string length?

The issue isn’t with mod_security as it’s not triggering any issues there, it seems to be solely related to the string length.

Thanks

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    Solved this myself after some heavy searching, the issue was the setting CURLOPT_BUFFERSIZE which limits itself to 512k by default.

    Increasing it to the amount of bytes / characters in the string fixed this, as did extending the timeout settings, see below:

    curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_BUFFERSIZE, 1000000);
curl_setopt($ch,CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_CONNECTTIMEOUT , 30); 
curl_setopt($ch, CURLOPT_TIMEOUT, 300);

  2. 0

    It looks like you’re encountering an issue where cURL in PHP is not able to handle a response of a certain size. There could be several factors contributing to this, including memory limitations, timeout settings, or some other server-side constraint.

    Here are some steps to debug and potentially resolve the issue:

    1. Increase PHP Memory Limit

    If the script is running out of memory, you can increase the memory limit by adding the following line at the top of your script:

    ini_set('memory_limit', '512M'); // or even higher if necessary

    2. Increase cURL Timeout:

    You might also want to increase the cURL timeout settings, as fetching a large amount of data may take longer. You can adjust the timeout using:

    curl_setopt($curl, CURLOPT_TIMEOUT, 300); // 5 minutes

    3. Check for Errors

    Ensure that you are checking for cURL errors after executing the request. This might give you more information about what’s going wrong:

    $err = curl_error($curl);
if ($err) {
  echo "cURL Error: " . $err;
}

    4. Increase POST Size (if applicable)

    If you are sending a large amount of data via POST, you may need to increase the POST size limits in your PHP configuration (`php.ini`):

    post_max_size = 64M

    5. Check Server Configuration

    If none of the above steps work, it might be worth checking with your hosting provider or inspecting the server configuration. Apache, Nginx, or other web servers may have limits that need to be adjusted.

    6. Debugging cURL Directly

    You can use command-line cURL to test the endpoint directly (outside of PHP). This might help you narrow down whether the issue is with PHP or something else:

    curl -X GET "your_url_here"

    7. Consider Chunking the Response

    If it’s not feasible to handle such a large response in one go, you might consider changing the way your server sends the response. You could split it into chunks and handle it piece by piece on the client side.

    Remember to restart your web server (Apache, Nginx, etc.) if you make any changes to the server configuration files.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search