Link to home
Start Free TrialLog in
Avatar of justmelat
justmelat

asked on

PHP 4.3, Apache2.2 issue

We are using curl with a php4.1.3 app.  It was running fine, connecting to another server.  This past weekend, they migrated the other server now, I am getting several CURL errors such as:

2011-05-10 08:15:45 --> Account Id =1249, CURL Error No: 7, CURL Error: socket error: 111
2011-05-10 08:15:45 --> KT Response: OP - GetProjectTemplateList
 

2011-05-10 08:15:45 --> ERROR : OP  GetProjectTemplateList - Empty response

The errors are sporadic, sometimes they work and sometimes they don't so we want to try adding a while loop to see if that will get it to work if it tries more than once, so I think want I want to do is have to, if error message ="CURL Error No: 7", run the code again, 4 more times.  Does that make sense of it there another/better way to do this?
Avatar of betopa
betopa
Flag of Mexico image

Most hosters are blocking several ports, sockets, functions... etc. for "security" reasons. Ask the "other server" hoster if they could be blocking cURL functions and ask them to allow cURL at laest for your virtual host. I recommend to solve this directly in the configuration servers, your code solution works fine por me, but its not the most optimal.
Good grief!  Get OFF of PHP 4.x completely and ASAP.  It has not been supported for ages.  After you do that, please post a copy of the script that is getting the errors, thanks.
Avatar of justmelat
justmelat

ASKER

Ray_Paseur:

I wish that were an option,but right now it is not.  Too many clients with custom app on that version of php.
ASKER CERTIFIED SOLUTION
Avatar of justmelat
justmelat

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Too many clients with custom app on that version of php. - you might want to tell them that they have serious security exposures as a result of being on a PHP4 application, and give them a cost based proposal to purchase the new, PHP 5 version of the custom app.  Just a thought...
Server admin finally figured this one out.