Statistics: Posted by jerpatvas — March 10th, 2011, 6:08 pm
(s2Member). Bug fix. A common error that site owners see in s2Member's log file is `unable to verify POST vars`. This is due to issues with various hosting companies not being configured with either cURL and/or `allow_url_fopen = on`. However, we recently discovered that WordPress® ( i.e. via `WP_Http` class ) will attempt to officially verify the SSL certificate issued through remote connections to Payment Gateways integrated with s2Member. This can cause an additional roadblock on some servers, because often they are not capable of officially verifying SSL certificates. They lack the extended configuration necessary to do so. In other words, this default behavior in the `WP_Http` class file can ultimately lead to `unable to verify POST vars` in s2Member. To workaround this compatibility issue, s2Member now specifies `sslverify = false` in communications to Payment Gateways. This should work to further eliminate sightings of this error in your log files. Also important to note; this does NOT pose a security issue, because all communications with Payment Gateways have authentication mechanisms already in place. Either through explicit API Key validation or through checksum verifications.
Statistics: Posted by Jason Caldwell — March 10th, 2011, 2:17 am
Statistics: Posted by jerpatvas — March 9th, 2011, 2:40 pm
allow_url_fopen = On
;extension=php_curl.dll
extension=php_openssl.dll
allow_url_fopen = On
<?php
ini_set("display_errors", true);
ini_set("error_reporting", E_ALL);
echo file_get_contents("https://www.paypal.com/");
?>
Statistics: Posted by Jason Caldwell — March 9th, 2011, 7:06 am
Statistics: Posted by Jason Caldwell — March 9th, 2011, 6:57 am
Statistics: Posted by jerpatvas — March 8th, 2011, 11:53 pm
Statistics: Posted by Jason Caldwell — June 23rd, 2010, 2:39 pm
Statistics: Posted by Guest — June 7th, 2010, 10:32 pm
Statistics: Posted by Guest — June 7th, 2010, 7:04 pm