By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,120 Members | 1,958 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,120 IT Pros & Developers. It's quick & easy.

PHP & Authorize.net w/o cURL?

P: n/a
Does anyone know of a way to use PHP /w Authorize.net AIM without using
cURL? Our website is hosted on a shared drive and the webhost company
doesn't installed additional software (such as cURL) on the server because
of that. Our site will have an SSL certificate next week, so I would like
to use AIM instead of SIM, however, I don't know how to send data via POST
over https and recieve data from the Authorize.net server over an https
connection. Does anyone have experience with this?
--
William C. White
Jul 16 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Jon Kraft <jo*@jonux.co.uk> wrote in message news:<Xn**************************@130.133.1.4>...
"William C. White" <u2***@hotmail.com> wrote:
Does anyone know of a way to use PHP /w Authorize.net AIM without
using cURL? Our website is hosted on a shared drive and the webhost
company doesn't installed additional software (such as cURL) on the
server because of that. Our site will have an SSL certificate next
week, so I would like to use AIM instead of SIM, however, I don't know
how to send data via POST over https and recieve data from the
Authorize.net server over an https connection. Does anyone have
experience with this?


You could use fsockopen (search for "POST" in the User Contributed Notes):
http://uk.php.net/fsockopen


AFAIK, you cannot post data via fsockopen() to https server...

---
"If there is a God, he must be a sadist"
Email: rrjanbiah-at-Y!com
Jul 16 '05 #2

P: n/a
ng**********@rediffmail.com (R. Rajesh Jeba Anbiah) wrote:
Jon Kraft <jo*@jonux.co.uk> wrote:

You could use fsockopen (search for "POST" in the User Contributed
Notes): http://uk.php.net/fsockopen


AFAIK, you cannot post data via fsockopen() to https server...


Since v4.3 there are different stream transports available (tcp, udp,
ssl..). If PHP is built with OpenSSL, you can use them, e.g.:

$fs = fsockopen("ssl://www.secureserver.com", 443);

http://uk.php.net/manual/en/transports.php

HTH;
JOn
Jul 16 '05 #3

P: n/a
Jon Kraft <jo*@jonux.co.uk> wrote in message news:<Xn**************************@130.133.1.4>...
ng**********@rediffmail.com (R. Rajesh Jeba Anbiah) wrote:
Jon Kraft <jo*@jonux.co.uk> wrote:
ng**********@rediffmail.com (R. Rajesh Jeba Anbiah) wrote:
> Jon Kraft <jo*@jonux.co.uk> wrote:
>>
>> You could use fsockopen (search for "POST" in the User Contributed
>> Notes): http://uk.php.net/fsockopen
>
> AFAIK, you cannot post data via fsockopen() to https server...

Since v4.3 there are different stream transports available (tcp, udp,
ssl..). If PHP is built with OpenSSL, you can use them, e.g.:
I see...
$fs = fsockopen("ssl://www.secureserver.com", 443);

http://uk.php.net/manual/en/transports.php


This manual page is not clear to me especially the "Table J-1.
Context options for ssl:// and tls:// transports (since PHP 4.3.2)"
There is no information about where to use the parameters like
"verify_peer". If you know more about the stuff, you may add some
useful user notes there---that will be really helpful to others.


I don't know, that stuff seems relatively new,


Yes. When I moved to PHP 4.3.1, I've looked at the changelog
which said fsockopen() can handle ssl://. I tried a lot, but it failed
--- I think, I've used a wrong port.
but I should think you'd
use them as additional directives in php.ini? Someone?
PS: On this page is an example of posting to a secure server (Example 2):
http://uk.php.net/manual/en/ref.stream.php


Thanks for pointing me this page. Nice example, but no info
about "certificates", "verify peer" stuffs.

I feel, cURL is so handy than this fsockopen() version.

---
"We live to die; we die to live"
Email: rrjanbiah-at-Y!com
Jul 16 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.