Comments on: How to: PECL HTTP request exception and error handling http://www.mkfoster.com/2009/01/06/how-to-pecl-http-request-exception-and-error-handling/ Misadventures in Technology Sat, 28 Jan 2012 19:56:42 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Michal Kočárek http://www.mkfoster.com/2009/01/06/how-to-pecl-http-request-exception-and-error-handling/comment-page-1/#comment-143 Michal Kočárek Thu, 02 Sep 2010 18:10:42 +0000 http://www.markfosteronline.com/?p=183#comment-143 PECL HTTP library seems to use the „pipelining“ feature of cURL, which somehows caches the open handles for next HTTP requests. I minimized the amount of produced error just by calling http_persistent_handles_clean() before each HttpRequest. This solution has minimized the amount of errors to minimum. PECL HTTP library seems to use the „pipelining“ feature of cURL, which somehows caches the open handles for next HTTP requests.

I minimized the amount of produced error just by calling

http_persistent_handles_clean()

before each HttpRequest. This solution has minimized the amount of errors to minimum.

]]> By: Bas Tard http://www.mkfoster.com/2009/01/06/how-to-pecl-http-request-exception-and-error-handling/comment-page-1/#comment-65 Bas Tard Wed, 25 Feb 2009 20:54:50 +0000 http://www.markfosteronline.com/?p=183#comment-65 I've been getting too many exceptions using HttpRequest::send() of this type: HttpInvalidParamException with message "Empty or too short HTTP message: ''" and inner exception HttpRequestException with message "a timeout was reached; connect() timed out!" The frequency at which this occurred was suspicious so I wrapped the send() in a loop of max 3 attempts and now the code always works even though the 1st attempt sometimes fails. I've had this same problem on different servers with different OS' and different code so there's obviously something broken in the PECL http code. I decided to replace all the PECL Http code and this ridiculous workaround with CURL code and I haven't had a problem since. I’ve been getting too many exceptions using HttpRequest::send() of this type:
HttpInvalidParamException with message “Empty or too short HTTP message: ”” and inner exception HttpRequestException with message “a timeout was reached; connect() timed out!”

The frequency at which this occurred was suspicious so I wrapped the send() in a loop of max 3 attempts and now the code always works even though the 1st attempt sometimes fails.

I’ve had this same problem on different servers with different OS’ and different code so there’s obviously something broken in the PECL http code.

I decided to replace all the PECL Http code and this ridiculous workaround with CURL code and I haven’t had a problem since.

]]> By: How to use the PHP cURL module to make HTTP requests from PHP - Mark Foster’s Blog http://www.mkfoster.com/2009/01/06/how-to-pecl-http-request-exception-and-error-handling/comment-page-1/#comment-51 How to use the PHP cURL module to make HTTP requests from PHP - Mark Foster’s Blog Sun, 22 Feb 2009 04:15:11 +0000 http://www.markfosteronline.com/?p=183#comment-51 [...] How to: PECL HTTP request exception and error handling [...] [...] How to: PECL HTTP request exception and error handling [...]

]]> By: Dan Delaney http://www.mkfoster.com/2009/01/06/how-to-pecl-http-request-exception-and-error-handling/comment-page-1/#comment-30 Dan Delaney Thu, 05 Feb 2009 20:54:44 +0000 http://www.markfosteronline.com/?p=183#comment-30 THANK YOU for this info about the undocumented "innerException" crap. Now I'm finally seeing what the error REALLY is. THANK YOU for this info about the undocumented “innerException” crap. Now I’m finally seeing what the error REALLY is.

]]>