Description: ------------ I'd like HTTP_Request to support CURL (or Net_CURL), if that's possible and if it supports all functionality.

This is outside the package's scope. Consider using the Net_Curl package: http://pear.php.net/package/Net_Curl

I have to agree that this would be a very good idea. And I don't see it being beyond the scope of HTTP_Request. HTTP_Request already utilizes the openssl extension, why shouldn't it use curl as well, if it's available. It could use openssl by default, and curl if it is installed and openssl is not installed or not providing the necessary features (like HTTPS proxies). Packages and applications could then rely on HTTP_Request doing the best thing available, and don't have to develop the same kind of wrapper again and again. I actually plan to drop native curl support in the SOAP package and rely solely on HTTP_Request, but if you really refuse to consider integrating curl support, I would have to rethink this decision.

I had similar but a bit deeper problem. sockets aren't allowed here and network connections may be only opened using extensions like curl, ftp, imap etc. So, I'd even prefer curl before trying other methods.

I'm currently toying with the package to try to implement a cURL backend to HTTP_Request while preserving BC. I am not planning on using Net_Curl at the moment because the current implementation doesn't add much to it in this case, and there's no good reason to add an extra layer. With a cURL backend, Net_Curl could even be deprecated in the future. It also seems to me that HTTP_Request is not optimized to upload large files, but that's a different topic. -Philippe

Did you make any progress already? Btw, you can probably use a lot of code from SOAP/Transport/HTTP.php.

Moving feature requests to HTTP_Request2.

cURL support added in HTTP_Request2 0.1.0