PHP & Authorize.net w/o cURL?

[William C. White]

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

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: PGP 8.0 - not licensed for commercial use: [url]www.pgp.com[/url]
Comment: You really should protect your privacy!

mQGiBD3dmakRBAD1cyMfBtE9eINVv4DcFI7cxp+ou6Y/8WqgZxZNtk2QWUeT9gs1
iCgAsmAw1841AFXcg677dZowJT8IBDadf82o8DLNYymHqcUANv T0hSyweEx7dMfz
Az1e61+ufIxWMKkle4IPaGajCzb6Ox47fBvEwYZAEwV3/x7ghOuUX6KPlQCg/wOZ
RbNGxPu3NBDgQ84FDbeZoCMD/2m8nPCJD+6DFlC9vyzxvHEaZE403gCG3FEQgRfW
AqM4PLLDs7tKcvYIpwQf0SCuUTwZIUBpmm5as6j28GO/D1STVBwI7jFt5Dpu323z
XBA5hhI02boRwf0zf8ELg7OSGqgAqC/ZRQnGIHtzqbNDJ/ker1qdo4Mxzwun1Iwr
bHQwA/9PVQWJU9mlvRaGPg/LxFkk6dXUuhPTc9R2n/2YENwLXgEb8WxiCW5hBSyz
lzlUqPwIoc0vyXXMHOjbbCgJp9kfaGI2SHTeV9GKTxh33G1dVU 0Mk5DUbzcWeK2X
Hu6b9YfbHl/EhDG1Wi4NjQkfNWjzXEadYfe4isDmKX1q+QBahLQoV2lsbGlhb SBD
dXJ0aXMgV2hpdGUgPHUyaWxsQGhvdG1haWwuY29tPokAWAQQEQ IAGAUCPd2ZqQgL
CQgHAwIBCgIZAQUbAwAAAAAKCRBCYmJsMyLtl+c/AKCrXj73n8Ss5P7RJq4K2N5R
I8qluwCfTdUGTebngPHGAFnlXZY2FBt7oWO0K1dpbGxpYW0gQ3 VydGlzIFdoaXRl
IDx3d2hpdGVAY2hhbWluY

[R. Rajesh Jeba Anbiah]

Jon Kraft <jon@jonux.co.uk> wrote in message news:<Xns93A46BADADBE7jonjonuxcouk@130.133.1.4>...

> "William C. White" <u2ill@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):
> [url]http://uk.php.net/fsockopen[/url]

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

[R. Rajesh Jeba Anbiah]

Jon Kraft <jon@jonux.co.uk> wrote in message news:<Xns93A46BADADBE7jonjonuxcouk@130.133.1.4>...

> "William C. White" <u2ill@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):
> [url]http://uk.php.net/fsockopen[/url]

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

[Jon Kraft]

[email]ng4rrjanbiah@rediffmail.com[/email] (R. Rajesh Jeba Anbiah) wrote:

> Jon Kraft <jon@jonux.co.uk> wrote:

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

>
> 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);

[url]http://uk.php.net/manual/en/transports.php[/url]

HTH;
JOn

[Jon Kraft]

[email]ng4rrjanbiah@rediffmail.com[/email] (R. Rajesh Jeba Anbiah) wrote:

> Jon Kraft <jon@jonux.co.uk> wrote:

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

>
> 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);

[url]http://uk.php.net/manual/en/transports.php[/url]

HTH;
JOn

[R. Rajesh Jeba Anbiah]

Jon Kraft <jon@jonux.co.uk> wrote in message news:<Xns93A563A3B8E73jonjonuxcouk@130.133.1.4>...

> [email]ng4rrjanbiah@rediffmail.com[/email] (R. Rajesh Jeba Anbiah) wrote:
>

> > Jon Kraft <jon@jonux.co.uk> wrote:

> >> [email]ng4rrjanbiah@rediffmail.com[/email] (R. Rajesh Jeba Anbiah) wrote:
> >> > Jon Kraft <jon@jonux.co.uk> wrote:
> >> >>
> >> >> You could use fsockopen (search for "POST" in the User Contributed
> >> >> Notes): [url]http://uk.php.net/fsockopen[/url]
> >> >
> >> > 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);
> >>
> >> [url]http://uk.php.net/manual/en/transports.php[/url]

> >
> > 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):
> [url]http://uk.php.net/manual/en/ref.stream.php[/url]

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

[R. Rajesh Jeba Anbiah]

Jon Kraft <jon@jonux.co.uk> wrote in message news:<Xns93A563A3B8E73jonjonuxcouk@130.133.1.4>...

> [email]ng4rrjanbiah@rediffmail.com[/email] (R. Rajesh Jeba Anbiah) wrote:
>

> > Jon Kraft <jon@jonux.co.uk> wrote:

> >> [email]ng4rrjanbiah@rediffmail.com[/email] (R. Rajesh Jeba Anbiah) wrote:
> >> > Jon Kraft <jon@jonux.co.uk> wrote:
> >> >>
> >> >> You could use fsockopen (search for "POST" in the User Contributed
> >> >> Notes): [url]http://uk.php.net/fsockopen[/url]
> >> >
> >> > 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);
> >>
> >> [url]http://uk.php.net/manual/en/transports.php[/url]

> >
> > 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):
> [url]http://uk.php.net/manual/en/ref.stream.php[/url]

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