updating from an intranet

Yeah this just assume a direct connection to the internet and fails. PLEASE include support for specifying a proxy server and port number.

You can set the 'update_status_fetch_url' variable to the URL you want to fetch from instead. There's no UI for this, but you could set it via:

A) previewing a php filtered page as an admin that contains:

variable_set('update_status_fetch_url', 'http://your.proxy.here:port/release-history/');

B) In the $conf array in your settings.php files.

That changes where update_status tries to fetch its results from. The default URL is 'http://updates.drupal.org/release-history'. Is that all you need? I confess I'm not too familiar with different kinds of proxy servers and what configuration they require. Please let me know if this is all you're asking about. Thanks.

This is actually an issue with drupal_http_request() and the use of fsockopen, I believe, and might be best served by a bug report against Drupal core.

http://api.drupal.org/api/function/drupal_http_request/6

See also this post.

Also try: Get me past my proxy server (http://drupal.org/node/7881).

I haven't been able to get Update Status to successfully check, but at least the admin pages load quickly. You can also turn off the Update Status module and ignore the Drupal warnings until Proxy support has been added to the core.

(Version: Drupal 6.0).

I have managed to get this working in 6.x by changing the update_fetch_url variable (not update_status_fetch_url as suggested in #2) by adding the following to my settings.php:

$conf = array(
    'update_fetch_url' => 'http://localhost:8888/release-history/'
    );

and then using a combination of the following apache rules:

ProxyPass /release-history/ http://updates.drupal.org/release-history/
ProxyPassReverse /release-history/ http://updates.drupal.org/release-history/
ProxyRemoteMatch ^.*/release-history/.*$ http://localhost:4444/

and using a cntlm (http://cntlm.sourceforge.net/) service running on port 4444 of the server box to authenticate with an IIS proxy firewall.

Note that my server is running on port 8888, adjust the URL in settings.php accordingly for your installation.

@yellek re: #5: that's great, thanks for sharing. in 6.x the variable name changed when the module was renamed on its way into core, but the same solution should work in either version with the right variable name.

It'd be nice to document this somewhere beyond this issue -- for 5.x I could put it in the README.txt and update the FAQ on the project page. not sure where it'd have to go for 6.x since it's now in core and there's no module-specific README.txt. Probably a handbook page somewhere. If anyone has specific suggestions or wants to just document themselves, please do. Thanks.

subscribing

Subscribing.

solution #2 doesn't seem to work with an authenticated access to the proxy :-(

Duplicated: #349375: Sometimes update_help() execute ages, Drupal freezing

Drupal 5 is no longer officially supported. If you think this issue is still relevant in 7.x and beyond, feel free to re-open.