Hello peterH
In my case, the approach i use in set two NetTalk or NetSimple Object in the web server procedure. One is without any encryption and the second is always with encryption.
one is called ThisWebServer and the secure one is called ThisSecureServer. The ports needs to be different in the two objects. The unsecured one run in standard port 80 and the Secure Server in the standard port 443 (you can use the ports you want or even make it variable)
This approach makes the application SSL ready out of the box.
Virtually you can access the app in both ports.
Usually in the future, the client wants to change the unsecured port to a secured one, but without using the
https://mydomain:443To make the transition easy to the client, i set an embed point with this code
IF GloSSLFlag = 1
ThisWebServer._AlwaysRedirect = 1
ThisWebServer._RedirectToHttpsPort = 443 !or your preferred secure port
END!If
The embed point is set at the Enter Procedure Scope in the Window Manager
The trick here is, if a user hits the unsecured server in port 80 without encryption, the web server redirects the user to the secure port.
In my case works like a charm. I think may be useful to you too.
If you need an example let me know, but example web9 Always SSL use a similar approach