Would it be possible to use non-SSL traffic (port 80) for your static and dynamic content URLs while you are using SSL traffic (port 443) for your environment URL? I have been able to get the documentViewerField working on an environment using port 443 for all 3 of my URLs, but I would like to try a mixture of 443 and 80. Instead of having to deal with two more SSL Certificates per year, I would just like to rely on the single certificate we already get each year for our main domain, and not worry about it for the 2 new domains.
Current working configurations using all https:
conf.suite.SCHEME=httpsconf.suite.SERVER_AND_PORT=env.domain.usconf.suite.STATIC_SERVER_AND_PORT=env.domain-static.usconf.suite.DYNAMIC_SERVER_AND_PORT=env.domain-dynamic.usconf.suite.DISABLE_STRICT_DOMAIN_SECURITY=true
In addition to custom.properties, there are 3 VirtualHosts in the Apache conf that are all port 443.
I have a feeling this will not work, as the SCHEME must be set to http or https, but I figured I would give it a shot.I would like to be able to do something like this:
conf.suite.SCHEME=httpsconf.suite.SERVER_AND_PORT=env.domain.usconf.suite.STATIC_SERVER_AND_PORT=env.domain-static.us:80conf.suite.DYNAMIC_SERVER_AND_PORT=env.domain-dynamic.us:80conf.suite.DISABLE_STRICT_DOMAIN_SECURITY=true
Then have a VirtualHost for the main domain be 443, and 2 VirtualHosts for the static and dynamic content URLs be 80.
Is something like that possible? I have tried that, but the document viewer is showing connection errors. I have also tried using self cut SSL certs, but the document viewer then gives trust errors.
Any thoughts/tips would be much appreciated!
Edit: It is worth noting that these are development environments with no sensitive data. I am not worries about non-SSL traffic here.
Discussion posts and replies are publicly visible