>> So does this mean that only one program at a time can use port 443?
Brian, yes.
The base rule is: 1 server = 1 port.
Howecer, you can "trick" to run several webserver on the same port 80. This is done by te MultiHost-program, which receives all input on port 80 (being a proxy) and then sort out, which data-packet was meant for which server behind the MultiHost. It reaches the data-packet to the intenden server now. For the remote user it look completely transparent, as if there is only one server running.
The MultiHost uses the names given to the servers, to decide, what the hand where.
An alternative is using the Apache as a reverse proxy for the same purpose. The Nettalk MultoHost is much more comfortable and convenient, its the first choice for this purpose. However, it requires the webserver to be DLLs and compiled with the same version - at least I recall to have read that.
If you have a mix of webservers from different Nettalk versions, you then could'nt combine them under the MultiHost. (always under the assumption that I recall correctly)
If this scenario occurs, you may use the Apache solution, utilizing its "vhost" ability.
See
Apache As A Reverse Proxy For Clarion Web Servers http://archive.clarionmag.com/cmag/v9/v9n02proxy.htmlAnyway, this reverse proxying does not work that easily for SSL-secured websites.
This has to do with the sequence, how client and server communicate. Usually the client sends a request, the server picks it and processes it accordingly. Either it responds directly (if the server was approached directly and has the port on its own), or (in case of the revery proxy) its hands the data packets further to the actually meant server, which then responds through the proxy.
When a clients tries to connect to a secured website, it first asks for the certificate, before it decides to connect to the server. This certificate is somehow tied to the server, which occupies the secured port. Thus, only one webserver per IP can use SSL.
Again however, there is another trick, at least for the Apache, to overcome that. Unfortunately I did not completely understand, how they do that trick and I am also not sure, whether those servers have to be under the label of Apache or if this expands to Nettalk Webserver also, just llike none-secured NTWS can be vhosts under Apache.
See
https://wiki.apache.org/httpd/NameBasedSSLVHosts