Closed (fixed)
Project:
Drupal core
Version:
6.0-rc1
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Dec 2007 at 18:15 UTC
Updated:
9 Mar 2008 at 23:15 UTC
After Upgrading from Beta 6 to RC1, Drupal is now giving this error in the admin control panel. "HTTP request status Fails"
Due to this OpenID and Feed Aggretation are no longer functional in RC1.
I don't know enough to look at the code, but I wanted to report this error.
Comments
Comment #1
MasterSushi commentedThis ended up being an issue with my webhost, and not with Drupal, that occurred at the same time as my upgrade to RC1.
Comment #2
kiakanpa commentedcould you please explain the problem as i am getting this issue too. I am unaware of any changes with my webhost.
Comment #3
aniruddhamallik commentedyeah.. same problem for me too... any ideas?
Comment #4
thememex commentedAny of you behind a firewall or proxy?
Comment #5
dana_johnson commentedI am having this same issue, the site is behind a firewall. Any pointers would be appreciated!
Comment #6
thememex commentedPlease see the following post: Get me past my proxy server (http://drupal.org/node/7881).
This is an issue in the Drupal core (drupal_http_request - common.inc). Now that Update Status is a part of core, and recommended to by on by default, a lot more folks are finding themselves with this issue if they are behind a corporate or web host proxy/firewall. Any outbound request for module/core updates, RSS feeds, OpenID authentication, etc will be blocked by the proxy/firewall. And there's currently no where to specify a proxy.
With Update Status in particular, every single admin page will call this function to check for updates. This is by design and works great when you have direct connectivity. Without direct connectivity, you'll notice a 10-15 second lag on every single admin page load. And that can be (very) annoying.
Comment #7
dana_johnson commentedI made a hack which works for me now, maybe this info would help others...
My site is within my company's intranet. Our proxy server is configured such that I need to send request to it only for locations outside the firewall, that is, internal paths will not be routed. So I hacked in a crude test for intranet versus internet paths in drupal_http_request(). Here are some snippets:
The function I added:
The proper solution would be to define "no proxy" domains and test for those before routing the request to the proxy server.