We made the poodle update to our site this evening and are getting the following after the update:
(28) Operation timed out after 60000 milliseconds with 0 bytes received
Any thought son what might be causing this?
We made the poodle update to our site this evening and are getting the following after the update:
(28) Operation timed out after 60000 milliseconds with 0 bytes received
Any thought son what might be causing this?
Did you apply DrByte's fix? Thread here http://www.zen-cart.com/showthread.p...ghlight=poodle
Can you run curltester and see if it reports any issues?
I ran the CURL tester and everything came back fine. I am stumped. I tried it on another site and it is the same deal. Must be something either with the fix I put in or something with my server.
The fix works fine, have it working on a number of sites (1.5.1 and 1.5.3).
Can you compare the files in includes/modules/payment to the corresponding files in a freshly downloaded ZC version that matches your installation and see if there are any differences (minus the applied fix)? Use something like WinMerge or Beyond Compare...
Maybe I am just doing it wrong:
<?php
/**
* paypal_curl.php communications class for PayPal Express Checkout / Website Payments Pro / Payflow Pro payment methods
*
* @package paymentMethod
* @copyright Copyright 2003-2014 Zen Cart Development Team
* @license http://www.zen-cart.com/license/2_0.txt GNU Public License V2.0
* @version GIT: $Id: Author: DrByte Sat Nov 2 12:51:04 2013 -0400 Modified in v1.5.3 $
*/
/**
* PayPal NVP (v61) and Payflow Pro (v4 HTTP API) implementation via cURL.
*/
class paypal_curl extends base {
/**
* What level should we log at? Valid levels are:
* 1 - Log only severe errors.
* 2 - Date/time of operation, operation name, elapsed time, success or failure indication.
* 3 - Full text of requests and responses and other debugging messages.
*
* @access protected
*
* @var integer $_logLevel
*/
var $_logLevel = 3;
/**
* If we're logging, what directory should we create log files in?
* Note that a log name coincides with a symlink, logging will
* *not* be done to avoid security problems. File names are
* <DateStamp>.PayflowPro.log.
*
* @access protected
*
* @var string $_logFile
*/
var $_logDir = DIR_FS_LOGS;
/**
* Debug or production?
*/
var $_server = 'sandbox';
/**
* URL endpoints -- defaults here are for three-token NVP implementation
*/
var $_endpoints = array('live' => 'https://api-3t.paypal.com/nvp',
'sandbox' => 'https://api-3t.sandbox.paypal.com/nvp');
/**
* Options for cURL. Defaults to preferred (constant) options.
*/
var $_curlOptions = array(CURLOPT_HEADER => 0,
CURLOPT_RETURNTRANSFER => TRUE,
CURLOPT_TIMEOUT => 45,
CURLOPT_CONNECTTIMEOUT => 10,
CURLOPT_FOLLOWLOCATION => FALSE,
//CURLOPT_SSL_VERIFYPEER => FALSE, // Leave this line commented out! This should never be set to FALSE on a live site!
//CURLOPT_CAINFO => '/local/path/to/cacert.pem', // for offline testing, this file can be obtained from http://curl.haxx.se/docs/caextract.html ... should never be used in production!
//CURLOPT_SSLVERSION => 3,
CURLOPT_FORBID_REUSE => TRUE,
CURLOPT_FRESH_CONNECT => TRUE,
CURLOPT_POST => TRUE,
);
That is correct. But there are two files where the changes are needed - one for paypal pro. Just checking but are you only using PayPal Express? I'm not seeing any timeout errors across all the sites (50+) I've made the changes on.
I am seeing a weirdness where that ssl message is cropping up in the middle of working paypal orders so I personally believe that PayPal themselves might well be tinkering with something still. They haven't been transparent about this change at all. Just saying.
The full-time Zen Cart Guru. WizTech4ZC.com
Bookmarks