Hi,
I'm not completely sure if this is the right spot to post this issue but I don't want to... well, anyway...
Here's a weird problem that I ran into. I have two freshly installed versions of Drupal (locally -> xampp1.6.8).
I have D6.8 and I just installed D6.9. The problem is that I get the following error only in D6.9 (in../?q=admin/reports/status):
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 bizarre thing is that I can't recreate the same error in D6.8 not matter how hard I try.
Both versions are fresh installs with OpenID, Aggregator disabled.
Therefore I'm wondering if anyone has an idea why that would be happening.
I did read a bunch of posts related to this particular issue (e.g. http://drupal.org/node/245990) but I just don't get why the problem would appear only in the new version (D6.9). I have tried 3 new installs of D6.8 and 3 new installs of D6.9, with the same result.
Any suggestions are greatly appreciated!
Thank you!
Comments
Howdy, I just upgraded to
Howdy,
I just upgraded to 6.9 and am having the exact same problem. I even read through that issue you linked to. Even though it looks like they resolved it in there, it was only for 6.8. So if I tried applying the fixes in that thread, I would have no idea weather they would work or not.
Just wanted to let you know that you're not alone.
-Benne
HTTP request status fails with D6.9
Hi I have 2 completely separate domains, both running D6.8
And both show the same HTTP request status fails error after upgrading to D6.9
Then I created a small test domain with D6.8 upgraded to D6.9, error shown. Downgrading to D6.8 does not help.
grtz,
Twan
theoretically should not be a problem
The real question is whether requests actually fail (eg. you cannot use update module, it says you have no data). In Drupal before 6.9, Drupal actually blocked HTTP requests when it thought you have no connection. Now it just always tries, so if you have some network outage, the next time it comes up, Drupal will work. This error is just an indication that Drupal thinks it cannot make these requests, it does not mean it does not try to do it on every occasion.
So is it actually working apart from this error message, or it is really broken?
It appears that the site is
It appears that the site is working correctly. And that it does fetch the update status of the modules. I only know for sure when one of the modules actually has been renewed, and the update status reflects this.
I will keep an eye on this.
grtz,
Twan
test install
You can always test by adding an older version of a new module you'd not use otherwise and see what update status says.
Update module?
Is the "Update" module (that fetch information about new versions of Drupal and modules) enabled on your installations?
yep
yep
Any more details on the
Any more details on the configurations that fail would be helpful - do you have something unusual set for the site's front page or any redirects in your .htaccess file?
---
Work: Acquia
---
Work: BioRAFT
I don't think so
I had a fresh install of 6.8. No errors, everything was running fine. I installed it a few days ago to play around, and the only custom module I added was Activity Stream. Besides that, everything was a stock 6.8 install. As I was about to add feeds to Activity Stream, I noticed the update message. So I updated to 6.9, following all the steps in the UPDATE readme. I load it back up and get the http request error.
So I tried to revert back to 6.8, following the same update steps. That worked insofar as it recognizes it as 6.8 in the Administer panel, but I still get the http request error. So, because this was a clean install with nothing in it, I decide to completely start over. I remove all the Drupal files, delete the mySQL database, and start from scratch with 6.8. After that is done, no errors.
This makes me wonder if it has something to do with the database, but that's just a stab in the dark.
On a side note: even if Drupal does still work with this error, a false positive should not just be ignored.
In my case disabling the
In my case disabling the update_status module helped out!
It somehow has to do with your provider not allowing http-outmessages or something like this.
Greetings,
Martijn
www.trekking-world.com
is not ignored
Well, it is not ignored, we are here, asking questions to help diagnose the problem :)
asking questions
Hi.
No problem with asking questions.
What do you want to know?
I have setup with D6.2 and upgraded 6 times until it was working flawlessly on D6.8
After upgrading to D6.9 I get the false negative HTTP request.
My board has only Garland as theme, and I have installed a number of modules through pluginmanager. But they were all working without any problem on D6.8
.htaccess file is the one supplied with D6.9 (only added "AddHandler x-httpd-php5 .php" to turn on PHP 5 but this worked on all previous versions of Drupal)
PHP version = 5.2.4
MySQL version = 4.1.21-standard-log
Regarding testing with an older module:
With PluginManager I installed CCK2.0
Without "turning on" CCK I went to the update report, and got reported immediatly that CCK has a newer version.
I also noticed that plugin manager has a new version.
So the site is working, but why the false positive?
What else would you like to know?
grtz,
Twan
D6.8 to D6.9
Hope my added input helps (1st post on this site!)
Same issues using the standard download.
No tweaks or even content created by me.
My setup is a Vista PC running WAMPserver.
Apache/2.2.6 (Win32) PHP/5.2.5
MySQL 5.0.45
The error showed before and after running update.
Count me in!
I upgraded this a.m. from 6.8 to 6.9 and now have the HTTP request status fails error.
I did not have the error before the upgrade.
Michael Krapf
The Graphic Design Shop
www.thegraphicdesignshop.com
Same problem but got working again
I upgraded from 6.8 to 6.9 and experienced the same problem. It was working fine in 6.8 and then in 6.9 saw the HTTP failure notice.
After a few attempts to get going again it eventually came back to life so my status page and update report page are both indicating my Drupal system is up to date.
Unfortunately I cannot say for sure what steps are required to get the HTTP requests working again but this is approximately what I did:
I was doing a few other things with the site at the time, hence not sure exactly what steps rectified the problem, but hope this helps a little.
Nope, thats not it
Hi.
I tried:
1. disable Update module
2. run cron manually
3. enable Update module
4. run cron manually
And I'm sorry to say, but that is not it. At least not for my site.
grtz,
Twan
This just worked for me...
I had this problem, AND couldn't check for updates for a while. My webhost (midphase - anhosting) had to put drupal on their "white list" of their firewall. Prior, it was getting blacklisted automatically (they removed it from there 3 times before realizing to put it on the white list).
So, I tried your instructions once again - I disabled the Update Status module, ran cron, enabled the Update Status module, and ran cron again. No more HTTP request status fail message. Now the only message is that I've got at least one update to take care of. ;0)
Also, these variables were set to "On" by my web host in trouble-shooting before I tried this (in my php.ini file - not always there by default):
Here's the section in the php.ini file:
The lines allow_url_fopen and allow_url_include may both have to be set to On - I'm not 100% positive about it, but that's what they tried.
And yes, I did not have ANY of these issues when running Drupal 6.8. It was after I had clean installed D6.9 in place of D6.8 - new database, the whole works - that I began getting ANY of these issues - I'm wondering if somehow the new Drupal code is triggering something on server firewalls??
HTTP request status error
I upgraded from 6.8 to 6.9 and now have the HTTP request status fails error.
I did not have the error before the upgrade.
Same problem here
same problem with me on a fresh upgrade geee :D
Me too. Got my sysadmin
Me too. Got my sysadmin working on it on his end and me on mine. Hope someone discovers a cure. :)
Downgrading to 6.8 did not fix it for me. Also. backing up the DB and Drupal Directory, ERASING the DB and Drupal Directory, and starting from scratch with a fresh install of 6.9 still yields the error.
hmm...
i was beginning to feel bad about NOT upgrading yet (i've just been lazy), but now it looks like my laziness has actually paid off.
other than that message, is everything working properly on your sites?
i'm thinking it might be wise for me to just wait a little to see if this problem gets fixed.
FYI I did some more testing.
FYI I did some more testing.
Same server:
1. Erased entire install. sites and database.
2. Installed 6.8 - did not gett the upgrade error problem.
3. Erased entire install. sites and database.
4. Installed 6.9 - DO get the Problem
5. Erased entire install. sites and database.
6. Begin reimplementing things on 6.8 and waiting patiently for resolution to this.
In otherwords. Good Idea on the waiting. :)
I made the http request problem error go away
I had the HTTP request status Fails message show after I installed drupal 6.9, below is what I did previous to the message disappearing, whether or not it was just a coincidence or an actual solution I don't know as I'm very new to Drupal and well.. don't really have a clue!!
1. Disabled all my modules
2. Ran cron
3. I downloaded and installed this module http://drupal.org/project/http_request_fail_reset
4. Activated all my other modules including the http_request_fail_reset module
5. Went into the http_request_fail_reset module setting and changed interval to minutes
6. Ran cron again
7. Did a cheesy fist pump and treated myself to a bit of chocolate cake
Would be interested to see if this works for anyone else?
works on my test site
Hi
I installed the module on my testsite, installing, enabling no other actions.
And the message was gone immediatly.
Will try one of my mainsites now.
grtz,
Twan
it also worked, but...
After installing the module, I had run Cron manually, receiving this error:
$fails = TRUE
Then returned to the status page, ran Cron manually again, no error, and false positive HTTP request failure was also gone.
I set the "http request fail reset" module to reset once every 4 weeks.
I wonder if the message will return or not.
grtz,
Twan
Nope, thats not it
Today, the message returned.
So the workaround with the HTTP message request module works only termporarily.
grtz,
Twan
But it worked for me
Thanks for posting this Twan - this was the only thing that worked for me.
I repeated the steps you described and got exactly the same result. So far it's not returned. And for what it's worth, I'm running D6.10. I've also installed the http_request_fail_reset module and maybe this is helping.
Fingers crossed...
Unable to fetch the updates!
The HTTP request status Fails message is gone but i'm not able to fetch the updates yet!!!!!!!!!
Thanks for this
Hey Roland!
I'm not one for leaving comments, when i'm scouring the net for drupal solutions, but i gotta say, this http request status fail, really frustrated me, i searched and searched for a remedy to this, but to no avail....that was until i read your post.
I am soooo happy for this, if you were a Londoner, i would have bought you a cake :-) ta, very much!
I don't have the issue
I installed Drupal 6.9 on my web site, and I don't have any problems on getting informations about the new module versions.
Whenever I check it manually or Drupal checks it automatically, I don't get the message error described here.
-- Kiam
Kiam la luno renkontas la sunon
Hi, May be it is only on
Hi,
May be it is only on updating and not on a new install?
Isn't it related to: http://drupal.org/node/346285 somehow?
greetings,
Martijn
I meant I updated Drupal
I am sorry for the use of the wrong word; I meant that I updated Drupal from 6.8 to 6.9, and I don't have the issue described here.
-- Kiam
Kiam la luno renkontas la sunon
After I updated to 6.9, my
After I updated to 6.9, my two sites become blank in firefox.
First it did run update.php successfully, but later the whole site is blank. Even I replace with 6.8 it still shows nothing.
I got the following messages.
[Fri Jan 16 15:10:28 2009] [error] PHP Fatal error: Call to undefined function _system_theme_data() in /home/***/public_html/***/includes/theme.inc on line 459
...includes/menu.inc on line 449
.../includes/menu.inc on line 410
Upgrading from 6.8 to 6.9 causes HTTP Request Fail error
Adding my situation to the mix.
1. Upgraded from 6.8 to 6.9 on a live site successfully with no error messages.
2. Upgraded from 6.8 to 6.9 on a local test site (using Uniform Server) and got the error message.
Feeling lucky on the live site. Still trying to figure out how to get rid of the error on the local site.
It would be interesting...
... to find out what is the difference between the live site, and the local test site.
It seems that the problem is caused by the configuration of the server. Maybe the new version supposes the server has the support for some functionality that is not always present.
-- Kiam
Kiam la luno renkontas la sunon
Brief History of my
Brief History of my situation: http://drupal.org/node/359049#comment-1202717
I migrated the 6.9 install with error from local server to hosted server...the error disappeared!
It has stayed gone for over 24 hours with multiple cron runs, both manual and scheduled.
?
Michael Krapf
The Graphic Design Shop
www.thegraphicdesignshop.com
Update on the Upgrade from 6.8 to 6.9 http error
The difference between the 2 sites was quite a bit. The live site is on Drupal Value Host and is a CiviCRM 2.1 site as well. The local site was a new one I had just started using Ubercart and assorted modules. The recent changes made to the local server (uniform server) was to enable cURL and add the ssleay32.dll and libeay32.dll to the usr/local/php folder but I don't think it's a server issue.
1. I tried doing a fresh install of 6.9 but still got the error.
2. I tried reverting back to 6.8 but got a strange problem with not being able to change my input format settings. I could create new settings but could not select the radio button to change from filtered HTML to full HTML.
3. In the end, I downloaded a fresh copy of 6.8 from CNET (as I couldn't find it on the Drupal site.)
4. Created a new database and installed 6.8. I tested to make sure I could change the input formats, made a few basic setting changes like time, etc. but did not enable any custom modules.
5. Then I backed up the 6.8 database and folder, downloaded a new copy of 6.9, deleted everything except my sites folder and upgraded to 6.9 successfully!! No problems. So far so good.
6. Then I enabled my theme and installed the following modules: admin, cck, link, date, event, fckeditor, imce, job search, print, toke, webform, ubercart, views.
7. And then....I re-created all of my content....ugh!!!
8. The next thing I'm going to try is installing the latest version of CiviCRM 2.14.
Unfortunately, this doesn't really explain what happened but it reminds me to backup everything (next time) and follow the upgrade instructions to the letter next time, i.e., setting it in offline mode, changing theme back to Garland and disabling all contrib modules.
Note: I did back everything up but did not change the theme or disable the modules for the live site so I just consider myself damn lucky at the moment.
My updating to Drupal 6.9 is
My updating to Drupal 6.9 is OK.
http://drupal.org/node/360358#comment-1207042
subscribing
subscribing
System Module
I have the same problem with http request fails in D6.9. I tried to change the module /modules/system/system.module line 1868.
$result = drupal_http_request(url('', array('absolute' => TRUE)));
with
$result = drupal_http_request(url('http://www.drupal.org', array('absolute' => TRUE)));
(see http://drupal.org/node/346929)
Now I have no error message in status report, but I don't think changing the system.module is a good solution. Any ideas?
OK, a couple things worth
OK, a couple things worth pointing out:
As for why people are seeing the error message, there are two possibilities:
In order to help fix this, it would be useful to know if anyone who is experiencing this problem has command-line (shell) access to their webserver? If so, it would be helpful if you could log in to your webserver and run a command similar to this (or anything else that allows you to fetch a webpage via the command line):
(where you replace http://www.example.com with the actual address of your website) and then also run this:
Then, paste the output you get back into this thread... thanks!
(The reason for doing this is that it sounds likely that people are facing the problem described at #346929: Http request status fails after upgrade to 6.8, where the hosting company's firewall is preventing requests to the server itself but allowing them to the outside world. The above test would allow us to compare.)
OK, a couple things worth
To be clear, you are expecting shell access to fail on
and work for the local wget?
I use wget local to my WAMP server at home, but get the error message,
so I do not think that is the problem, unless I have misunderstood you?
The is not firewall issue at home.
(I hesitate to update the hosted site - I think I may just do a dry run with
a test site to see what happens.)
OK, a couple things worth
Taking my dry run from my local test page that began as 6.8 then upgraded to 6.9
No content ... then uploaded that to my HostGator account and I did a fresh configure.
No status errors.
I am thinking it may be a difference in the Apache Server on my local machine.
I'm not so adept to sort out the differences. :(
BTW, I know wget works with my shell account - I've used it to collect stat values from Stanford.
My best guess is actually
My best guess is actually that for people seeing the error but who know that outbound HTTP requests are working on their machine (if the update status module is working correctly, for example), they would have
wget http://drupal.orgreturn normally, but the local wget (probably would be something likewget http://localhostif Drupal is installed on a home computer) to have some kind of major problem when it is run.Either way, it would be useful to see what kind of message is returned in each case... The most important thing is the returned HTTP status code (if there is any), since that is what Drupal 6.9 is using to determine whether the error message should be printed.
Thanks!
Hmmm
Off my local machine. (The root says 6.8, but its upgraded.)
Off my HostGator.com
I also upgraded my live site since the dry run went well.
(Kudos to HostGator, since it works without the error.)
Not sure what the
"HTTP request sent, awaiting response... 301 Moved Permanently"
means, but maybe its a clue?
On my Vista machine I have http://unxutils.sourceforge.net/ for wget and other great scripts.
If I go to the index.php, it looks as good as the live site.
drupal_http_request() works on redirections
I checked the function that should be called in such cases, and if it gets an HTML error code like 301, 302, or 307 it makes the request for the new location returned.
If that is the function to fail, the reason could be
fsockopen()which returns an error for some reasons.It would be useful to know which is the error message that people are seeing, because if
drupal_http_request()gets an error that is not an HTML error, it returns a negative error code.The redirection you are seeing is caused by .htaccess that redirects from http://localhost to http://localhost/.
Agreed, the above one is
Agreed, the above one is very puzzling. It's hard to see from the code at http://api.drupal.org/api/function/drupal_http_request/6 why a redirect would cause any kind of problem -- it seems like it should work fine with a normal HTML code returned and then everything else should work correctly.
Maybe a fresh pair of eyes can figure out what might be going wrong here?
Results from wget - and my fix/workaround?
I ran wget as requested and both calls worked OK.
wget http://zeus.cs.salford.ac.uk/project/
--2009-01-20 16:19:58-- http://zeus.cs.salford.ac.uk/project/
Resolving zeus.cs.salford.ac.uk... 127.0.1.1
Connecting to zeus.cs.salford.ac.uk|127.0.1.1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html.4'
wget http://drupal.org
--2009-01-20 16:20:44-- http://drupal.org/
Resolving drupal.org... 140.211.166.6
Connecting to drupal.org|140.211.166.6|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html.5'
I, too, had had no problems until I upgraded my sites to D6.9. In my case I had 14 sites to upgrade on the same server. Each site had a separate copy of the Drupal PHP code, separate apache config settings, etc., though these are essentially the same structure. Of these 14 sites 9 had the HTTP request problem and five did not!
In every case my Apache config forces a redirect to use https when you login, so the request to view the status page used https. If I refreshed the status page the error message remained. However, simply altering the URL in the browser to use http, rather than https, to view the status page caused the HTTP Request error to go away. It did not return if I subsequently used https to view the status page. Strange!
I don't know if this will enlighten anyone.
Tony
Eur Ing A.M.Addyman
School of Computing, Science and Engineering
University of Salford
Salford
M5 4WT, United Kingdom
I may have an idea what's
I may have an idea what's going on here, actually -- I think when you access your admin page via https, the HTTP request check defaults to trying to access your front page via https also, and somehow that request doesn't work cleanly. If so, this might be an interesting edge case that needs to be considered.... hm.....
The reason the error doesn't return once it's been cleared is that the admin page doesn't always do the check (it does it the first time you visit that page, and after that only if there was a failure while trying to make another request).
In my case the downgrade was
In my case the downgrade was necessary at least temporarily because the checking that drupal 6.9 was doing was 'bogging down' the page load on the order of 30 seconds or so for every attempt.
so while it may still work, the slowdown made it unusable.
Interesting point... sounds
Interesting point... sounds like in order to get that slowdown you have a case where the request to your local machine is being blocked completely.
You should be able to bypass the check for now by putting this in your settings.php file, though:
And then Drupal 6.9 will work fine without the 30 second slowdown. Hopefully, as time goes on and the various edge cases get solved, the slowdown (if it happens at all) will only be for people who truly have a broken Drupal installation anyway... :)
workaround
adding your line to settings.php removed the error message, added new life to my test site regarding speed, and enabled automatic login once again. I hope someone comes up with the cause and solution to this. This error did not occur with my other test site using drupal 6.9 but an older version of xampp.
http_request_fails setting
I initially saw this problem initially at around v 6.4 when I installed the webserver authentication module and enabled NTLM access for the site. At that time I followed the recommendations I found on the forum (including the settings.php mod) and was able to make the problem 'go-away'. This worked fine until I did the 6.9 upgrade. Now I'm getting the error again with the settings.php mod still in place.
same problem...
I've upgraded today, yes I know I'm too lazy... Same problem, all people, the most strange thing is something similar happened some weeks ago with a friend's wordpress cms...
With the trick of the http module, this works but is a little weird... The only good thing is the important sites are with drupal 5 :D
Oh, and if I execute the wget I received the correct transition...
same problem
Installed 6.9 on a WAMP, windows 2003. worked without problems.
Installed 6.9 locally, on a dev machine, WAMP but Vista and I got this error.
Since I also experienced the slow page load I went for the temporary settings.php fix which makes working locally possible.
I tried to figure out what is causing this but I fear someone with more understanding of networking needs to look at this.
It's so pretty being green!
It's so pretty being all in the green once again! See my post earlier. The one guy's instructions worked for me. Someone else fixed it by another method, I believe. If I'm not mistaken, the problem is 2 fold for many (I know it was for me): Drupal somehow getting blacklisted on firewalls, and then the http_request status getting "stuck" in "failed" mode somehow in the database. By swapping things around like the site being in online or offline mode (maintenance), you seem to be able to trigger clearing out the http request status field/table/whatever in the MySQL database. So if one way didn't try another. Another individual had to turn off all developer modules - so if the easy one didn't work, try that one, it could be you have another module requesting the HTTP Status Request, keeping it stuck - just a guess on my part, anyway.
I've gotta contact my web host, so they know it's fixed! ;0)
HTTP Request Nightmare
I must say I am new to using Drupal. I installed Drupal 6.9 with Apache and MySQL on both my work computer (XP) and my home laptop (VISTA). I am getting the HTTP error on my Vista machine only. I found the following solution online and am eager to get home to see if it will work on my Vista machine. If anyone tries this today, let me know how it goes.
Drupal and Apache in Vista: some tips http://greenash.net.au/posts/thoughts/drupal-and-apache-in-vista-some-tips
Thursday, 5 June, 2008.
I bought a new laptop at the start of this year, and since then I've experienced the "privilege" pile of festering camel dung that is being a user of Windows Vista. As with most things in Vista, installing Drupal and Apache is finickier than it used to be, back on XP. When I first went through the process, I encountered a few particularly weird little gotchas, and I scribbled them down for future reference. Here are some things to look out for, when the inevitable day comes in which you too will shine the light of Drupal upon the dark and smelly abyss of Vista:
1. Don't use the stop / start / restart Apache controls in the start menu (start > programs > Apache > control), as they are unreliable; use services.msc insetad (start > run > "services.msc").
2. Don't edit httpd.conf through the filesystem — use the 'edit httpd.conf' icon in the start menu instead (start > programs > Apache > configure), as otherwise your saved changes may not take effect.
3. If you're seeing the error message "http request status - fails" on Drupal admin pages, then try editing your 'c:\windows\system32\drivers\etc\hosts' file, and taking out the IPv6 mapping of localhost, as this can confuse the Windows mapping of 127.0.0.1 to localhost (restart for this to take effect).
4. Don't use Vista! If, however, you absolutely have no choice, then refer to steps 1-3.
HTTP Request Fail Error message
Okay so I went home and put a # in front of the "localhost 127.0.0.1" in the c:\windows\system32\drivers\etc\hosts file and it DID NOT work!!! BUT THEN i put a # in front of the "::1" and voila, it fixed the error message and made loading localhost in my browser way faster than it was loading before. Note: You must restart your machine for the change to take effect.
Thanks to all for the support in solving this irritating error message. I do believe that it relates to using Drupal 6.9 on Vista, because the error does not show up on my XP machines at all.
I hope this helps, good luck to everyone out there
Peace, love and happy website building with Drupal
i put a # in front of the "::1" and voila
"i put a # in front of the "::1" and voila"
My Vista64 tells me I don't have permission?
(I am the administrator.)
Is there a certain way to make the change?
Ah http://geekswithblogs.net/thibbard/archive/2006/12/13/changingyourhostsf...
McAfee complained when I made the change.
I can report that my error is gone without any other change.
(My Ethernet does not have IPV6 turned on either.)
Thanks. Works like a charm now!
Vista, D6.9, WAMP
Subscribing
/grn
GrN.dk
Has this ever been resolved
Has this ever been resolved
I've loaded D6.9 onto Wamps 2of. Using Vista 64Bit OS.
I read something about the hosts file for vista being the problem.
Is there a support document that spells out the correct fix?
==============================
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.
==============================
RE: Has this ever been resolved
I've not tried putting back the hosts code since D6.10 release.
It would be interesting if it went away with the new release?
I suspect its still a problem, but limited in scope, if there are so few posts in this thread.
Worked, thanks guys
I had the "http ... fail" with looong delays on my Vista x64 with wamp.
Solution for me:
1. I started Notepad as Administrator (right-click Notepad icon/executable and select "Run as administrator")
2. Opened the hosts file "C:\Windows\System32\drivers\etc\hosts"
3. Deleted the line containing: "::1 localhost"
4. Saved file (if you cant save, you did not start Notepad as Administrator)
5. Worked instantly, no restart needed
THANKS for the tip.
Thanks x10
Noob / Vista / WampServer2 / Drupal 6.11 and had this problem. Also had it with a bitnami drupal stack install that I uninstalled.
hosts file initially just had the ::1 localhost line in int. I added a 127.0.0.1 to get phpMyAdmin working.
I could get updates, but had HTTP failure message.
Several hours of reading later, I commented out the ::1 line as above, and HTTP message disappeared.
Happiness ensues, although I not sure with this was a problem.
Drupal 6.12
I have Drupal 6.12 on midphase hosting and the response for this problem (only three days problem -to this date) was:
Hello,
I apologize but your server is now blocking outbound port 80 which is the port
HTTP requests are made on. This is because of security vulnerabilities
involved with this. Please let us know if there is anything else we can do to
assist you. Thank you.
--
Best regards,
What can I do?
I find it silly
I find silly that outbound requests for the port 80 are blocked; as it involves the server side (and not the client side), it can create problems only when the web site to which the outbound request is made is taken from a parameter passed in the URL. Then they should also not allow PHP pages to be served, because there could be security issues if the PHP code uses any parameters passed through the URL without to check them first.
Change provider; I have never heard of a server being forced to not accept outbound connections to port 80.
The solution from Midphase
Hello,
Midphase has disabled outbound port 80 because there are known security issues related to leaving this port open. To look for upgrades for Drupal, you will need to go to drupal.org and check for their posted updates. Drupal is offered through Fantastico, although the only support we offer is the initial installation. Once the code has been installed and modified by the client, it is up to the client to maintain their sites security and keep their version of Drupal up-to-date. Again, if you want to look for Drupal upgrades, you need to go to Drupal.org to see their available updates. Let us know if you have further questions.
--
Best regards,
Confusing
I disabled some modules and now it is OK. I report later which module is the reason for such confuse situation.
Please do..
Please do post what modules caused the situation. That'd be good info to have around.
This worked as well for
This worked as well for me.... very easy fix