Bruce,
In some cases we are running one app on different servers. Those are not the problem; however, we have four boxes with eight apps running on each, and one box with 22 apps running on it. At end state, we will have three or four servers running about 30 copies of my software on each, in addition to the 65 standalone servers. I have thought about using one copy of NetTalk to deliver content from all 30 apps, but it will require a considerable rewrite and, since we are busy installing, it may be a while before I can get to it.
The wildcard certificate is the best way to handle this, and using the Comodo wildcard it will only cost about $850/year to license the certificate for all the computers and systems. I have not priced this with Verisign yet, but I imagine that it is considerably more. I sure hope the FAA does not have an exclusive agreement with them.
Of course, the wildcard certificates require the domain name to be consistent. To that end, I have created a NS zone to manage and keep the URLs consistent. UPDATE: I was just advised that my request for a zone was disapproved for security reasons; therefore, I have just requested 111 names in the same domain with another 50 or so to come in the future. That request was approved - go figure!
The wildcard should be good for decrypting the SSL for all the instances of NetTalk on the server. I have established separate names for each of the sites on the server and directed them to the same IP address. I plan to run a NTWS on the default port, determine the intended destination from the original URL, append the port number and redirect the request to the appropriate server.
What variable (if any) contains the original URL? What show stoppers am I missing here?
Rob