Download of feed failed with code 0.

Thanks for opening this separate request.

I've just tried http://drupal.org/node/feed with a local install using the latest dev from CVS and found no problems.

PHP version 5.2.6
curl library available.

Could you post your PHP version and whether or not curl is available php -i | grep curl ?

My curl library is 7.19.5.

Could you go into libraries/http_request.inc and return FALSE from http_request_use_curl() and test whether the problem persists? I'd like to see whether it's curl that's acting up or whether we have something else going on in Feeds that doesn't play well behind a proxy (I know that Pubsub won't work, but that's not the issue here).

So, it stands to find out why the heck curl wouldn't be able to download a feed while drupal_http_request (PHP's fread()) can.

What response do you get if you run a

> curl -I http://drupal.org/node/feed

I get:

HTTP/1.1 200 OK
Server: Apache
X-Powered-By: PHP/5.2.12-pl0-gentoo
X-Drupal-Cache: MISS
Last-Modified: Fri, 26 Mar 2010 15:16:02 +0000
Cache-Control: public, max-age=60
ETag: "1269616562-0"
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Vary: Cookie,Accept-Encoding
Content-Type: application/rss+xml; charset=utf-8
Content-Length: 54368
Date: Fri, 26 Mar 2010 15:32:20 GMT
X-Varnish: 1847510823 1847468865
Age: 978
Via: 1.1 varnish
Connection: keep-alive

Looking at #2 (says there's curl present) I'm assuming that all that's missing is curl in your $PATH. Can you dig it up?

I get a lot of Download failed code -1003 error, even though my feed imported.

I was having this same problem. I'm working locally on a MAMP server with my sites set up as Virtual Hosts. We're behind a pretty fancy-schmancy network configuration here, so I wasn't sure if that had something to do with it or not. But once I had cURL return false, everything was golden.

It's beautiful.

Tank you, tank you, tank you. I'm not sure why it happened like that, but I'm going to set up a beta site on a live server to see how it goes.

Update:
The site worked wonderfully when I put it on the live server, until I updated the site. It's odd because I have cURL installed on the server. But when it returns false, it works fine.

Hi

Here at the Open University we are affected by this issue too. The cause is that we are behind a proxy server, and we aren't allowed to configure curl to go past the proxy. When trying to run curl from the command line an error occurs.

curl -I http://drupal.org/node/feed
curl: (7) couldn't connect to host

I cant remove curl as it is cloned from a standard linux machine, and curl is used to successfully access internal urls. I've patched the feeds module like everyone else to return false, but it would be nice to have a configuration option to decide whether to use curl or drupals http_get (also patched to allow access past the proxy server).

I'm happy to run any more tests you have or need regarding this.

Thanks
--
Stuart Crouch
(Open University Drupal Host Administrator)

> The cause is that we are behind a proxy server, and we aren't allowed to configure curl to go past the proxy.

If you were allowed, how would that configuration look like?

I just ran into the same issue and upgraded the module to beta4 and it is working once again. Worth a try for those who trip over this issue in the future.

Hi there,
I had also the same problem with the proxy, but only disabling the use of curl in the feeds module didn't do the job. I had to also apply the proxy patch under http://drupal.org/node/735420 to make it work.

Steven Jones suggests to make the usage of cUrl optional, I think that's a great idea and it would also address the issues discussed here.

I will mark this issue as duplicate as the new one is more general and encompasses this one:

#883342: Don't force usage of cURL

Hi,
I keep getting a similar error was womdering what had been found ?

Download of ftp://username:password@ftp.site.com/folder/folder2/feed.csv failed with code -1003