| Author |  |
kkaprielian
10/6/2005
7:56:34 PM | The "localhost" trick worked. I set "localhost" and the virtualdir to read something and the site comes up but no images - design images are there, so is IG editable text on homepage but no images through the IG interface.
Any link or login goes to a HTTP/1.1 404 Object not found error page. Other than that and an opening/closing html/body tags all on one line.. Not sure "who" is generating this.. The usual URL 404 in iis is set.
Sincerely,
Ken |
kkaprielian
10/6/2005
9:20:33 PM | Me again,
After you have a bunch of virtualdirs in iis and each IG settings.asp has been setup. Choose one site and make that the default site for localhost in iis. That one site will work. Then in iis admin you can quickly copy/paste the directories of each virtual dir into the main website to switch back and forth between a few. A bit wobbly but it works. |
admin
10/10/2005
8:41:52 PM | It sounds like a 404 handler problem. IG works by refering all images, and pages other than the home page to the URL specified in the error page settings.
It should be:
404 - /default.asp for a website or
404 - /demo1/default.asp for a virtual dir
BTW: I like your demo setting. I personally would make a default.htm that has links to each demo site. Thus you can pick a demo for each client on the spot.
-John |
kkaprielian
10/11/2005
4:41:20 PM | Thanks, I found this by trial and effort - now I'm onto why it seems to take so long to find a site.. I half think there's something to do with the various timeout settings in iss for script code. |
kkaprielian
10/12/2005
7:03:11 PM | Just to follow up. I found from Microsoft that if you use the IP address or better yet the name of the computer instead of "localhost" or the 127.0.0.1 loopback address that it does indeed appear to be faster. |
| |
