How to Verify PHP cURL Support and Diagnose Common Issues

Directly check phpinfo() for "cURL support"

This is the most reliable and intuitive method. The PHP probe essentially wraps phpinfo() or a subset, but many lightweight probes filter out module details, causing you to see "curl" text while it is actually not enabled. Open the full phpinfo() page in a browser (not the probe homepage) and press Ctrl+F to search for cURL support. It must appear in a separate table row with the value enabled to be truly supported.

If you only find the curl_version function but no cURL support: enabled, the extension failed to load or was disabled.

If no curl‑related sections appear at all, the extension is likely not loaded.

Some probes show the libcurl version, which is compile‑time information and does not guarantee runtime availability.

CLI php -m and Web page results may differ

PHP CLI (terminal) and Web SAPI (e.g., Apache or PHP‑FPM) often use separate php.ini files. Seeing curl listed with php -m | grep curl in the terminal does not guarantee it works in web pages, and the opposite is also true. This discrepancy is especially easy to miss in Docker, Baota, or similar environments.

Check the Web environment configuration: in the phpinfo() page, locate the "Loaded Configuration File" path.

Check the CLI configuration: run php --ini in the terminal.

Ensure both php.ini files contain an uncommented line such as extension=curl.so (Linux/macOS) or extension=php_curl.dll (Windows).

Using function_exists('curl_init') is not enough

The existence of this function only shows that the extension was once loaded; it does not guarantee the current context can actually use it. For example, the disable_functions directive may explicitly disable curl_init, causing the function to exist but any call to it to throw an error.

A more reliable approach is to run a minimal real request on the spot:

<?php
$ch = curl_init('https://httpbin.org/get');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$result = curl_exec($ch);
$httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
if ($result !== false && $httpCode == 200) {
    echo 'cURL 实际可用';
} else {
    echo 'cURL 加载了但无法完成请求：' . curl_error($ch);
}

Do not replace this test with file_get_contents() or get_headers(), as they may not use curl under the hood.

Low curl version can also cause functionality gaps (e.g., HTTP/3 or TLS 1.3)

PHP reporting curl support does not guarantee that all modern features are available. For instance, using CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_3 requires libcurl ≥ 7.66.0, and TLS 1.3 support typically needs curl ≥ 7.71.0.

Check the version: in phpinfo() look under "cURL Information → Version", or call curl_version() in code.

PHP 8.2+ provides the semantic function curl_up_to_date('7.66.0') for safer version checks.

Older systems (e.g., CentOS 7 with curl 7.29) may have the extension enabled but still lack support for HTTP/2 and newer protocols.

When troubleshooting, first confirm that cURL support: enabled truly exists, then verify that CLI and Web configurations are synchronized, and finally perform a real request to validate connectivity—none of these three steps can be omitted. Version compatibility issues are often mistaken for a non‑working curl, when in fact the functionality is simply missing, not the extension itself.