
Originally Posted by
ALiepinieks
In my ever so humble (and very recent) experience, I could forgive someone for thinking this. I recently had an issue where cURL seemed to be installed and working fine. Although not Auspost, ozpost or any other variation, one out every 5-10 of my cURL requests would lead to my script exceeding a server time out restriction, and no amount of debugging, logging, php error reporting, catch throw or ANYTHING (that I know of) seemed to let me know what the problem was (having said this I didn't have access to some of the server log files).
Anyway, I actually suspected it was Apache timing out, and finished up working around the problem by using multi cURL functions instead, but...
I mention this because:
a) Orien - even if you think it's cURL, then think you know it's cURL, the problem might simply appear to be occurring while processing a cURL request, and in fact not be cURL at all...
b) RodG - I can understand why someone might think cURL is the problem, as at times the lack of response from PHP error reporting can simply lead us up the garden path...
Andrejs