posted
Hi, I had no trouble getting Apache to run in Vista Home Premium using the tips found across the web as well as right here. The problem I am having is resolving to localhost. 127.0.0.1 will offer up the It Works! page but no go with localhost.
After scouring the internet for a solution, the only suggestion I have come across that works is to comment out the IPv6 entry in the hosts file - # ::1 localhost
While this works, is this really the best (or only) solution to use?
This doesn't seem like a Vista problem but more a problem with Apache (or more likely a problem with my lack of knowledge on how to configure apache). I installed Win32 Binary including OpenSSL 0.9.8i (MSI Installer)apache 2.2.11 straight from http://httpd.apache.org/download.cgi
Help is appreciated! Thanks.Posts:
7 | From:
Philadelphia, PA, USA | Registered: 02-02-09
posted
I forgot to mention, that I have purchased 3 books by Mr. Powers:
PHP Solutions PHP Object Oriented Solutions Dreamweaver CS4 with CSS AJAX and PHP.
I have only begun with PHP Solutions and as recommended in chapter 2, I would prefer to install Apache, PHP and MySQL manually and document the process, rather than use an all-in-one installer like XAMMP. (Although Mr. Powers, does recommend the simplicity of the XAMMP install in his Dreamweaver book which makes it tempting to take the easy route).Posts:
7 | From:
Philadelphia, PA, USA | Registered: 02-02-09
posted
I have never had any problem with localhost on Vista Business Premium, but localhost is simply an alias for 127.0.0.1, so it doesn't matter if you need to use 127.0.0.1 instead.
Although I have offered a lot of setup assistance over the years, it's impossible for a single person, like myself, to troubleshoot Apache, PHP, MySQL, and phpMyAdmin on the wide range of operating systems used by different people. That's why I recommended XAMPP (or MAMP for a Mac). Both are fine. The all-in-one solutions also have dedicated forums, where many more people are able to help with installation issues. Hopefully, that will leave me free to deal with scripting problems.
posted
Thanks for the response David. I finally traced the problem back to my antivirus solution. ESET NOD32 V3 was the culprit. The solution is to disable protection to the browser (not recommended), edit the hosts file removing the ::1 localhost entry or to use a different antivirus product altogether. NOD32 V4 Beta does not have this problem.Posts:
7 | From:
Philadelphia, PA, USA | Registered: 02-02-09
posted
Thanks for that information. I'm also using ESET antivirus v3, and haven't experienced any problems. However, I see that my Hosts file doesn't have an IPv6 entry. I'm not sure whether that's because I deleted it myself or because I bought my Vista computer in January 2007, when Vista was first released.
posted
Hello again... I just wanted to mention that Eset now has v4 available for download from their website free of charge for registered subscribers. You will of course need to provide user name and password that accompanied your purchase. The new version as promised has fixed the problem with IPv6 localhost ::1 and it no longer needs to be removed or commented out to work.
Next
