I think it would be beneficial to have the http request check system_requirements() be optional. A setting could exist on a form that would allow an admin to disable the HTTP request check during that function run.

The reason is this:

Let's say you have a server environment where you know the HTTP requests will fail. This means that every time you hit the admin overview page, your Drupal install will unnecessarily check an http request that will fail 100% of the time.

For me, this meant a 15 second hang up every time I hit the admin screen. I found a few patches out there that addressed this by making the http request timeout configurable, but that doesn't really address the fact that you're still allowing a timeout to occur each time you hit the admin overview.

If you as the Drupal admin know that HTTP requests will fail, then why allow Drupal to check this guaranteed failure each time you hit the admin page?

If there were a setting on the admin screens that allowed you to disable the http request check that is run in system_requirements() (this would only be checked when you know it's going to fail) then the unnecessary request and unnecessary use of server memory and unnecessary delays in admin page loading would be avoided.

Comments

superspring’s picture

superspring commented
Status: Active » Needs review

There is a variable named 'drupal_http_request_fails'. When this is TRUE it runs the HTTP checks, otherwise skips them.

"If you are certain that Drupal can access web pages but you are still seeing this message, you may add $conf['drupal_http_request_fails'] = FALSE; to the bottom of your settings.php file."

Status: Needs review » 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.