Topic awaiting preservation: Curl and Server stuff (Page 1 of 1)

Does anyone know what the problem is when you write this:

passthru( '/usr/bin/curl http://www.domain.com/');

and it works, but then you try to do it secure, like so:

passthru( '/usr/bin/curl https://www.domain.com/');

and it returns nothing? My hosting service says that they have openssl on there, and I pretty much trust them on that, so I don't think that is the problem.

can you see that site in a browser?
Here's the deal even though the URL's look similar they are actually usually 2 different site. When I've done this before there's always been a httpdocs folder for the http URL and a httpsdocs folder for the https site. So these do not actually resolve the same way.




.:[ Never resist a perfect moment ]:.

[This message has been edited by bitdamaged (edited 09-24-2002).]

Any suggestions on how I fix this? What I'm really trying to do is get it to pass info to Authorizes gateway server. If there is a different way to pass that than

passthru( '/usr/bin/curl -d "info_to_pass=infopassed" https://www.domain.com/');

then I don't know what it is. Either way, I checked with the authorize by making a live transaction and while it isn't sending me back info, it isn't posting to the server either. No record of transactions declined.

<edit>If you wanted to see it in a browser, it's https://www.gumpscookies.com/newpage.php or http://www.gumpscookies.com/newpage.php

and with trying to connect https:

https://www.gumpscookies.com/newpage2.php or http://www.gumpscookies.com/newpage2.php

</edit>


[This message has been edited by Red Ninja (edited 09-24-2002).]

I think it may be in your -d flag I haven't used curl but according to the man pages it looks like -d is only a flag for standard HTTP connections there's another flag -E for using this with certificates. Check out the docs about 2/3 of the way down.



.:[ Never resist a perfect moment ]:.

Huh. You're probably right. I'll check that out tomorrow. S'kind of wierd, though. Several third party scripts have specified the use of curl that way. Guess it just might be server configuration or something.

Thanks for your help, there, bitdamaged.