I realize that last time I didn't really explain the new web site structure.

| 
|--/                     root directory  
|--default.html          "choose a web site..."
|--missing.acgi          for redirections
|--error.shtml           NetPresenz error page
|--robots.txt            don't index /kcw
|
|--/aigg                 Apple Internet Gaming Group (home: www)
|--/crs                  Cirran Restoration Society  (home: www2)
|--/dsweet               Dave's Web Site             (home: www)
|--/kcw                  Kevin's Web Site            (home: www2)
|--/tartan               Tartan's Web Sites
|----/.                    Hudson Leick Gallery      (home: www2)
|----/alicia               Alicia Silverstone Gold   (home: www2)
|--/tgd                  TGD Web Site                (home: www)

All current links will still work. Redirections are now:

aigg.org                 www.tgd-inc.com/aigg/~
hudsonleick.com          www.hudsonleickfan.com/~
hudson-leick.com         www.hudsonleickfan.com/~
www.tgd-inc.com          www.tgd-inc.com/error.html
www2.tgd-inc.com         www2.tgd-inc.com/error.html

Remember, missing.acgi is called because of a page miss that is not caught by a subdirectory, so a miss in the /kcw directory hits its own missing.shtml file and is not handled by the redirection script. The other thing to note is that default.html is different for each site. It will point to www or www2 depending on the directory chosen. Naturally it should send the request to the home server of that web site, and if that machine is down the request will come back to the first server (because the second server will be spoofing the first server).

To do: I need to hopefully fix the .shtml files to include Apache Server Side Includes (and hope they don't conflict with NetPresenz SSIs). Other than that I think I can copy my web sites to Thales with no problems. Set Thales to search for index.html and then default.html so it doesn't try to serve up a Mac alias file. Set up Thales to redirect hudsonleick.com and hudson-leick.com (the other redirections are not really necessary).

You know, I also need to create a custom error page so that the Pictorious server says something sensical instead of a generic 404 error. Yes, 404 errors are useful but even more useful is information like how to report a problem and a link back to the site's main page. That way I can link back to port 80. Supporting 8080 was probably a bad idea and now I'm stuck with trying to phase it out without making inbound links fail.

It all started because TDG used to be a dedicated modem connection. We had one IP address back then and port mapping to send requests to the appropriate server. So back then, Thales had port 80 and Jennifer had port 8080. Once we got a business DSL line with 5 IP addresses servicing port 8080 requests was no longer necessary. But I stuck with it to keep it backwards compatible. I should have changed any inbound links I controlled to go to port 80, but I had some sort of worry that I might have to go back to one IP address in which case I'll need 8080 again. There is still that worry, but now I'm resigned to just use Thales if that happens (or I can arrange for an "accident" to fall on that infernal machine -- muhahaha!).