When drupal cannot access web pages the next message is showed:
"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."

Since a lot of times is a matter of putting the web page in service: admin/settings/site-maintenance . It will be nice to suggest to check the online status of the web.
Currently the message "blames the others" while it can be a simple matter in drupal.
Surely there are other reasons why this message shows up, but it won't hurt to add that small suggestion.
More info: http://drupal.org./node/245990

Comments

Slim Pickens’s picture

Slim Pickens commented

One main reason, as the error message suggests, is that your web server/host can't make direct http requests. Proxy servers and firewalls can prevent Update from working, for example.

Here are some topics that might help, or not.

http://drupal.org/node/222454

http://drupal.org/node/7881

BartVB’s picture

BartVB commented
Title: HTTP request status Fails » 'HTTP request status' failure message lacks information
Project: » Drupal core
Version: » 7.x-dev
Component: usability » system.module
Priority: Normal » Minor
Status: Closed (works as designed) » Active

I also just spent quite a bit of time hunting down a problem with 'HTTP request status: Fails'.

IMO it would be very helpful if the error message told the admin what URL it wants to open and what the resulting status code was. In case of jcampo that would have been '503 Service Unavailable', in my case it would have been '401 Authorization Required' which would have been definite hints towards solving this error :)

aren cambre’s picture

aren cambre commented
Priority: Minor » Normal
Issue tags: +Usability

Would also be nice if the error could link to a drupal.org page that has more guidance.

BrianY’s picture

BrianY commented

If you are testing a non-production (non-public) site with a Domain Name that has not been fully established within DNS, this error will definitely occur. Signs to look for are use of a HOSTS file modification on your development computer, that is not in place on the web server.

The error message should be more specific in its content. In this case it is not just that an HTTP request failed, but the domain lookup prior to the HTTP request. No request actually took place (request to where?).

To correct this issue, if you are using your site like this: add the domain name in question to your web server's host file.

aren cambre’s picture

aren cambre commented

This is happening on Dreamhost with a Drupal site behind a standard, public CNAME.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.