ID: 22441
Comment by: jvinet at zeroflux dot org
Reported By: eric at vlender dot com
Status: No Feedback
Bug Type: OpenSSL related
Operating System: GNU/Linux (slackware)
PHP Version: 4.3.1
New Comment:
I've had the same problem with the old/deprecated pfpro sdk and PHP
4.4.7.
When the extension is built into the php binary (--with-pfpro=DIR),
cURL breaks with https:// URLs.
When the extension is built as a shared module
(--with-pfpro=shared,DIR), cURL works.
Hope this helps, though in the long run, I'd recommend moving away from
any reliance on the pfpro SDK.
Previous Comments:
[2003-08-05 10:38:31] bduell at ncacasi dot org
I have verified, through VeriSign, that the SDK of PayflowPro
(currently, v. 3.06) is statically linked against the openssl
libraries.
They have no plans on changing this design, therefor we will be
changing payment processors.
Good luck!
[2003-03-09 19:15:13] [EMAIL PROTECTED]
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to Open. Thank you.
[2003-03-04 20:11:07] [EMAIL PROTECTED]
Does compiling PHP as DSO for Apache fix this?
If so, you can bogus this, we already have a report about that one.
[2003-02-28 19:19:56] eric at vlender dot com
Well, I have now compiled in openssl-0.9.7a and cURL-7.10.3 and instead
of just getting nothing, I get this in my logs:
[Fri Feb 28 18:19:46 2003] [notice] child pid 11916 exit signal
Segmentation fault (11)
[Fri Feb 28 18:19:46 2003] [notice] child pid 11908 exit signal
Segmentation fault (11)
That is with an attempted fsockopen(ssl://securehost.hre, 443,
errorno, error); call that works perfectly with out the -pfpro option
...
I guess I can always have PHP shell out to a PERL script and manage the
transaction ..
Thanks for your help :)
[2003-02-26 11:37:47] eric at vlender dot com
On a quick side note, Payflow pro is working perfectly. We use it for
our signups, and the signup procedure is functioning perfectly. Just
cURL and fsockopen() are not happy.. :(
I placed them in /usr/lib and /usr/local/include respectfully.
/usr/local/lib/pfpro.h is a symlink to the header in /usr/local/include
~ locate pfpro | sort
/usr/lib/libpfpro.so
/usr/local/include/pfpro.h
/usr/local/lib/pfpro.h
/usr/local/src/php-4.3.1/ext/pfpro
/usr/local/src/php-4.3.1/ext/pfpro/CREDITS
/usr/local/src/php-4.3.1/ext/pfpro/TODO
/usr/local/src/php-4.3.1/ext/pfpro/config.m4
/usr/local/src/php-4.3.1/ext/pfpro/pfpro.c
/usr/local/src/php-4.3.1/ext/pfpro/pfpro.lo
/usr/local/src/php-4.3.1/ext/pfpro/pfpro.o
/usr/local/src/php-4.3.1/ext/pfpro/php_pfpro.h
/usr/local/src/php-4.3.1/tests/testpfpro.php
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/22441
--
Edit this bug report at http://bugs.php.net/?id=22441edit=1
