php_curl does not work with IIS extended protection
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
Same issue described here:
https://github.com/curl/curl/issues/12511
a workaround would be to use the Schannel Backend instead of OpenSSL:
set CURL_SSL_BACKEND=schannel
https://curl.se/libcurl/c/libcurl-env.html
But this does not work for precompiled php binaries as libcurl is statically linked.
Would it be possible to add a php.ini setting to use a different curl backend? Or build php_curl with schannel backend on windows?
see https://curl.se/libcurl/c/curl_global_sslset.html
PHP Version
PHP 8.3.6
Operating System
Windows 11
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the php_curl extension, the php.ini setting idea, and curl_global_sslset, then compare the precompiled Windows build constraints with the Schannel workaround. Done would be a supported way to select a compatible backend for PHP 8.3.6 on Windows 11, or a confirmed Schannel-based build approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, php
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100