| T O P I C R E V I E W |
| Davio |
Posted - 08 June 2012 : 14:23:47
Previous versions of IIS, I had set it so that when I type in 'home' in my browser, it goes to localhost. At the moment, typing in 'home' does a google search for home.
I added a binding for 'home' to my default website, but that doesn't seem to work.
Is there something else I need to do? Do I need to hard code it in my HOSTS file so that it points to localhost? |
| 6 L A T E S T R E P L I E S (Newest First) |
| Carefree |
Posted - 09 June 2012 : 09:28:15
Yes, sorry, had a brain fart. Missed it altogether. |
| Davio |
Posted - 08 June 2012 : 21:14:41
It's IIS 7 Carefree. It's in the title. 
I had mentioned I had already set the bindings for the site already, but I decided to test it again. I moved an html file between the home and home2 site and realized that home2 is indeed loading the correct site. Just that what came up was not what I had expected. Seems it was taking the application variables from home site.
Anyways, thanks again Carefree.  |
| Carefree |
Posted - 08 June 2012 : 20:56:14
Which version of IIS are you using?
For IIS 6:
Open IIS, right-click the website; go to properties. Under the "web site" tab, click the "advanced" button. In the top section, "host header", add the 'home2' designation like this:
127.0.0.1 80 home2
For IIS 7:
Open IIS, click the site name. On far right, click bindings. Click "add". Type home2 in the field, save. |
| Davio |
Posted - 08 June 2012 : 20:30:25
Thanks guys. Did it and that worked. home loads my webpage locally.
Decided to create a 2nd site in IIS. Want to type 'home2' to get to this 2nd site.
Created the bindings for it, and hard coded it in the HOSTS file to point to 127.0.0.1.
But it is loading the default site.
From memory, I think HTTP headers was the way to go, to tell IIS which site is being loaded. I set the http headers for both the default and home2 as follows:
Default (home) site
Name: domain
Value: default
2nd (home2) site
Name: domain
Value: home2
Still loads the default site.
Made sure to give the 2nd site it's own application pool as well.
Any help on that? |
| Carefree |
Posted - 08 June 2012 : 18:46:35
Davio, localhost should always be hardcoded in the hosts file to "127.0.0.1". Every other entry there which you want to block could be coded to "0.0.0.0" (since that's an illegal address, it won't even bother looking on the local computer and will process slightly faster than using "127.0.0.1". |
| HuwR |
Posted - 08 June 2012 : 16:11:50
yes I would think so, it has no other way of knowing what 'home' means
|
