On 7/24/07, Bosky, Dave <[EMAIL PROTECTED]> wrote:
Yes. The script is the same on both machines.
I can pull up a web browser and connect to the ssl url that I'm trying
to connect using php/curl.
The only DLLs I need to add are libeay.dll, ssleay32.dll, right?
I'm running Windows 2003 Server with IIS 6.0
I believe so.
In order to enable cURL on a Windows box, you have to copy
libeay32.dll and ssleay32.dll from the DLL folder of the PHP/ binary
package to the SYSTEM folder. (to be safe, you may want to do both
C:\WINDOWS\SYSTEM\ and C:\WINDOWS\SYSTEM32\, but I think Windows
allows you to `copy *.dll C:\%SYSTEM% - I'm a *nix guy, but I think I
remember doing that on Windows a while back).
Then edit php.ini to remove the semicolon from the front of this line:
extension=php_curl.dll
That *should* do it, but I'm sure you've already done all of that,
so beyond that point, I'm not really sure what could be causing the
protocol error. In either case, I think it's definitely an SSL error
as opposed to a cURL/PHP one.
Sorry I'm not being much help on this one....
--
Daniel P. Brown
[office] (570-) 587-7080 Ext. 272
[mobile] (570-) 766-8107
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
