Ok, good to have this cleared up.

All I can say to this is that the libcurl.dll contained in the win32-devel
archive has been compiled with ssl support and works for me with a
dynamically linked curl executable (not publicly released).
I'll contact Amaury directly to take some traffic off the mailing list.

Jörn

> -----Original Message-----
> From: Daniel Stenberg [mailto:daniel_at_haxx.se]
> Sent: Monday, March 05, 2001 12:04 PM
> To: libcurl Mailing list
> Subject: RE: SSL CURL WINDOWS
>
>
> On Mon, 5 Mar 2001 Joern.Hartroth_at_comma-soft.com wrote:
>
> > Allright, let me try to understand this: You take curl.exe,
> libeay32.dll,
> > and libssl32.dll from the archives at the curl site, put
> all of them into
> > one directory which lies on the executable %PATH, and when calling
> > curl.exe on an https:// URL, you get the error below?
>
> I fear that is not the case. He is probably using apache and
> PHP on a windows
> box, and then his PHP program uses the curl module and *that*
> is accessing a
> https:// site and isn't working...
>
> The apache+php then needs a libcurl that works with it (as a
> DLL or whatever)
> and that is built to support SSL. Apache also needs to find
> all those DLLs
> when supposed to.
>
> --
> Daniel Stenberg -- curl project maintainer -- http://curl.haxx.se/
>
>
> _______________________________________________
> Curl-library mailing list
> Curl-library_at_lists.sourceforge.net
> http://lists.sourceforge.net/lists/listinfo/curl-library
>

_______________________________________________
Curl-library mailing list
Curl-library_at_lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/curl-library
Received on 2001-03-05