Given the way the web has evolved in years since ContentBox was released, handling SSL at the page-level no longer makes sense. The chances that one page would be upgraded while another would not are slim-to-none. Google, for example, downgrades the SEO of the page and shows it as insecure in their results if the connection is non-SSL - https://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.html

There is also a lot of introspection and needless conditionals around SSL in dealing with page relocation and generating navigation.

The suggestion is to make this setting a site-level setting - meaning that if a site connection needs to be upgraded, it should be done on the first client request to the site.

This will allow ContentBox to remove all of the redundant conditionals around page-level SSL and simply perform a one-time upgrade as necessary. This will also prevent issues when using reverse proxies and port handling, since all navigation links can now be relative.