0

I'm having trouble getting the CURL extension to work on PHP 5.5 ts-VC11 on Win7 64 bit. The supplied php_curl.dll loads but does nothing (doesn't register itself as a curl extension) without throwing any error.

I know there is a solution for running a patched php_curl.dll on PHP 5.3 and 5.4 on Windows 64 bit, but I have to use PHP 5.5 64 bit, and I can't find a working CURL extension for that.

Is there a solution?

Community
  • 1
  • 1
rustyx
  • 80,671
  • 25
  • 200
  • 267
  • One solution would be to use the 32bit version of WAMP. Afterall 64bit PHP on a windows environment is still flagged as Experimental on the PHP website. – RiggsFolly Nov 12 '14 at 11:50

2 Answers2

1

In WAMPServer version prior to 2.5:

All you need to do is copy libeay32.dll and libssl32.dll from the PHP \wamp\bin\php\{phpversion}folder to the \wamp\bin\apache\{apacheversion}\bin folder.

If you are using WAMPServer 2.5 you dont even need to do that as SYMLINKS should automatically get created for you. If the symlinks are not there then just do this to create them:-

wampmanager -> Apache -> Version ( and click on the version number you are using )

It is very bad practice when using WAMPServer to put anything in the \windows\ folder structure as this will cause problems when/if you decide to switch between versions of Apache and/or PHP.

RiggsFolly
  • 93,638
  • 21
  • 103
  • 149
0

It works now with the original php_curl.dll. The issue seems to have been a conflict in ssleay dll's. Just adding PHP to the PATH didn't solve the issue, but copying libeay32.dll and ssleay32.dll to C:\Windows\System32 did (note -- on WAMP its better to copy these to the Apache bin folder).

rustyx
  • 80,671
  • 25
  • 200
  • 267
  • You dont actually need to put them in either of these directories. All you need to do is copy libeay32.dll and libssl32.dll from the PHP folder to the Apache\bin folder. – RiggsFolly Nov 12 '14 at 11:58
  • I did it this way because my `apache\bin` folder already had newer versions of those DLLs, so I didn't want to overwrite those. But certainly it might have worked your way, too (I only needed this for local development on Windows, not for WAMP). – rustyx Nov 12 '14 at 12:20
  • Ok but the same applies even if you are not using WAMPServer specifically. If your Apache folder already had newer versions, where did they come from. Can I assume you have at least 2 versions of PHP available to you? – RiggsFolly Nov 12 '14 at 12:24
  • They came with the *[Apache 2.4.10 Win64](http://www.apachelounge.com/download/)* package from apachelounge. – rustyx Nov 12 '14 at 13:49
  • Yes, but a its PHP that is using these files the ones from the PHP delivery are the ones that should be used – RiggsFolly Nov 13 '14 at 00:57
  • `mod_ssl` from apache is also using those files. – rustyx Nov 19 '14 at 13:21
  • Yup, but as the ones that come with Apache dont normally work we copy the ones that come with PHP, which normally do work, over them. – RiggsFolly Nov 19 '14 at 16:07
  • Adding PHP's path to system Path variable worked for me. – estornes Dec 23 '16 at 17:40