News aggregator works properly when proper RSS feeds are added. When a malformed RSS feed is added, the news aggregator will fail to fetch the malformed feed. After the malformed feed is corrected, every other existing feed will not be able to fetch anymore feeds, and the following report error is shown:

***

HTTP request status Fails

Your system or network configuration does not allow Drupal to access web pages, resulting in reduced functionality. This could be due to your webserver configuration or PHP settings, and should be resolved in order to download information about available updates, fetch aggregator feeds, sign in via OpenID, or use other network-dependent services.

***

The system has to be restarted for the news aggregator to work again

Comments

unikbyte’s picture

This issue was seen in Drupal 6.2

Anonymous’s picture

Title: News Aggregator Fails to Fetch Feeds » HTTP request status Fails : News Aggregator Fails to Fetch Feeds
Project: New Aggregator for Drupal core » Drupal core
Version: » 6.2
Component: Miscellaneous » aggregator.module
Status: Active » Postponed (maintainer needs more info)

Moving to the appropriate location as this is not the right issue queue for the aggregator.module

Also, there are multiple threads about this issue and I'm pretty sure it's not a bug and is a 'By Design' security setting but I'll let someone else make that call.

jamesoakley’s picture

Version: 6.2 » 6.8

I've just had exactly this issue in Drupal 6.8.

One of the feeds I subscribe to was returning status code 410 (gone). Since the aggregator picked that up, the Drupal_HTTP_Request_Fails flag was set to true, and everything that follows from that happened.

jamesoakley’s picture

Priority: Normal » Critical
Status: Postponed (maintainer needs more info) » Active

Marking critical, because one badly formed feed into the aggregator, and all update checks, aggregator feeds, mollom requests, openid logins will fail

gábor hojtsy’s picture

Title: HTTP request status Fails : News Aggregator Fails to Fetch Feeds » News aggregator should handle more HTTP statuses
Version: 6.8 » 7.x-dev
Category: bug » feature
Priority: Critical » Normal

From what I see in the source code, when a feed is "broken", that is something else but status codes 304, 301, 200, 302 and 307, the feed is considered broken and a HTTP request check is issued. The "HTTP requests broken" flag is only set in Drupal, if and only if that check fails. So Drupal needs to *not* be able to request its local page (a condition a patch at http://drupal.org/node/245990 hopefully resolved, but not yet released).

The next try to query whatever non-broken should start working. I agree aggregator should be able to handle more status values, so it does not bork out status values like "410 Gone". Recategorizing for that.

ParisLiakos’s picture

Version: 7.x-dev » 8.x-dev
Status: Active » Fixed

Aggregator's default fetcher now in drupal 8 uses guzzle, so this should be no issue

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.