This is a discussion on localhost problem within the Windows Web Servers forums, part of the Web Server and Related Forums category; WHen I goto http://localhost/ nothing displays.. I get an "Unable to display page error" But if I ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
WHen I goto http://localhost/ nothing displays.. I get an "Unable to
display page error" But if I go to 192.168.0.100:8080 I see the index file. Why won't localhost work? |
|
|||
|
On 16 Jul 2003 15:10:42 -0700, The Other Guy responded to a post from
skadoesntsuk@somethingorother.com (Woody) who wrote in comp.infosystems.www.servers.ms-windows: >WHen I goto http://localhost/ nothing displays.. I get an "Unable to >display page error" But if I go to 192.168.0.100:8080 I see the index >file. Why won't localhost work? Well, you would have to put in http://localhost:8080 (which is really just like http://127.0.0.1:8080). Check for the Listen directive in the httpd.conf file. If you want to change your setup to run on just http://localhost you have to modify the Listen directive to read: Listen 80 This is the default port for Apache, so you don't need it when putting in the URL (in other words, http://localhost:80 works but the port # -- 80 -- is redundant in this case). You can mix and match IP addresses and different port numbers -- see http://httpd.apache.org/docs-2.0/mod...on.html#listen. Then just change the configuration of your router to forward requests to that IP machine to port 80 for web services (as well as any firewalls configured to filter traffic). HTH TOG -- ../configure --prefix=~/zyterion Not this guy or that guy, The Other Guy. This spot may contain a satirical comment or comedic source, and is meant to be funny. If you are easily offended, gullible or don't have a sense of humour we suggest you read elsewhere. |