– For HTTPS reverse proxy you need a certificate. For external usage you need a certificate that is trusted bij a external CA.
– Add Feature Content Switching, Load Balancing. (I Forgot it first time… always had a 503 error code…. i was sure the policy for content switching was ok….)
1. Make a Load Balanced Reverse Proxy.
1.1 Add a server. your real Webserver
1.3 Add a LB virtual server. And choose for example CookieInsert for persistancy.
1.4 Add your internal Certificate(from your internal domain CA) when it is a https connection to the back-end webserver. Bit length restriction for windows is 1024 bits. I recommend to use as low as possible for internal traffic. Less encrryption/decryption = less CPU usage.
1.5 Create a Content switching Policy.
1.6 Create a Content Switching Virtual Server. Bind the CSW policy. Select the created LB virtual server as Target.
1.7 Add the Cert that is trusted by a public CA to the SSL Settings
1.8 Add DNS entry CSWDEMO.DEMO.LOCAL 192.168.2.22