Hi Bill,
>> Is it a number or a string length ?
I'd say the only limit I can think of is perhaps the string length of the set:domains variable (on the window). Currently the length of that is 2K, but obviously could be larger.
That ultimately ends up in Net:SimpleSSLCertificateOptionsType.CertificateFile which has a size of NET:SSLListStringSize (currently 4K). (This _includes_ the path to the file though, so keep the certificates path short for maximum number of certs.)
Again, if this proved to be an issue, the field could be made longer.
>> Also, does anyone know a way to force nettalk to support ssl and non-ssl at the same time when multiple domains are used (some ssl some not).
The easiest approach is simply to have 2 web server procedures in the same app. One listening (and set up) on the insecure port, and one on the secure port. Personally where I've had this situation I've simply run 2 exe's on the server machine to keep things simple. Then the "insecure" server simply has a redirect page (to the secure address) for those sites that need it, and they server the actual site if not.
(Very quickly it becomes "why not just make them all secure?")
>> If the limit is low (say less than 100), does NT11 support more?
I can extend the limits (they are arbitrary) but yes, that would happen in NT11.
>> With NT11 do I get more granular control of domains and ssl (the hostname stuff appears to be down within the no-source code part of NT).
There's no difference (I can think of) between NT10 and 11 with regard to this - but I'm not sure the code you are wanting to add is in the non-source code. I _think_ you can do what you want in the server itself. But perhaps it's best if you give an example of the kind of granularity you are looking for - specifically - and I can give a suggestion for that?
cheers
Bruce
Topic: SSL Certificates and many domains (Read 2801 times)