Accessing AML via HTTP (not HTTPS) results in a timeout

Currently, accessing any AML URL via HTTP (not HTTPS) results in a timeout. This is because the load balancer that control access to AML environments listens only on port 443 (note that this is not currently the case for the 'demo' environments).

Appropriate behavior needs to be defined and implemented for access attempts via HTTP. Unless there are objections, I will implement a redirect to the root domain using HTTPS after the behavior of the root domain is defined.