can't find entry point nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation in DLL-file \php\ext\php_curl.dll

[aducom]

Description

When curl is enabled in the php.ini, then at startup Apache the error

can't find entry point nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation in DLL-file \php\ext\php_curl.dll

appears. Besides that, all seems to work well.

PHP Version

8.3RC4

Operating System

Windows 11

[ndossche]

Hmm this looks the same as #12218 (check edit history)
The solution written doesn't indicate much, but it suggests something is wrong with environment path?

[aducom]

The error message points to the correct location where the php_curl.dll is found. I have found 12218, but I could not decide if this is the same issue. All other PHP versions work fine, only 8.3 doesn't. If it's an environment path issue, then how to find out which path is wrong?

[ndossche]

Do you have a nghttp2.dll file, and if so, is it in the same directory as php_curl.dll ?

[aducom]

Actually I do have that file, but in the standard download of the Windows package the file is located in the php root folder, the curl in the ext folder. That is exactly the same for the other php versions (7.4, 8.0, 8.1 and 8.2)

[aducom]

I figured it out, at least I think so. The same file also exists in the Xampp apache/bin folder. I renamed that file, and all seems to work fine now. I would like to know why that file is there, which does not interfere with other php versions. But I'll install a fresh xampp to see if it is part of that package. Could be put there by accident.

[kallesommernielsen]

The version supplied with PHP is very much intended as the php_curl.dll is linked to a specific version of NGHTTP2 that you need to have available for the library (extension) to be loadable. What other projects does (like XAMPP) I can't say. However you should use great caution when mixing the DLL files by moving, deleting etc.

A dynamically linked library on Windows will be looked for in the %PATH% environment variable, along with the location of where the executable that spawned the process is located (like Apache's httpd.exe) or the library's current folder that is linked against the library.

This is not a bug on PHP's end, but a configuration error in the setup. I suggest you report this to XAMPP if it is an issue they supply a conflicting library in the same path for a PHP extension. An ideal solution would be to use the same version of the library, but it is difficult to guarantee.

[ndossche]

Agree with Kalle, please report this to XAMPP.

[globdug]

Hello,
I have encountered the same problem, but I'm using Laragon. I made some tests, I don't know if I have just wasted my time doing something useless, by the way the table below show which combination of Apache/PHP give this error.
Can it be useful? 😅

	apache-2.4.54-win64-vc15	apache-2.4.54-win64-vc16	httpd-2.4.55-win64-VC16	httpd-2.4.58-win64-VS17
php-8.1.24-Win32-vs16-x64	🆗	🆗	🆗	🆗
php-8.1.25-Win32-vs16-x64	❌	❌	🆗	🆗
php-8.2.12-Win32-vs16-x64	❌	❌	🆗	🆗