I can see where this might be helpful for some users (and therefore some admins) who might not always remember/know to specify https or forget the alternative port if 443 is redirected elsewhere.
Did you contact your support provider and get an "official" response?
My thoughts: Redirect port 80 on the UTM to a webserver that handles the redirection to the appropriate user portal (along with an HSTS header)?
Or if you don't mind potentially (likely?) running afoul of support: "/var/sec/chroot-httpd/etc/httpd/vhost" might hold potential as a starting point.
Just curious if this feature ever got implemented in 9.2 as per the feature request comments indicated (Webserver Protection: Redirect HTTP to HTTPS)? If so, where are the settings?
Please note that port 80 on the server is already being used by Web Application Firewall, and by the Web Filtering Transparent Mode AD SSO. The latter two had issues working together and needed additional configuration. Adding a third thing using this port will cause more conflicts.
Also note that the feature request above is for Web Application Firewall, not portal. Yes it is in 9.2. Look in the Virtual Webserver and select Type.
This is killing any attempts to update the webadmin cert using the HTTP-01 challenge with Let's Encrypt. Not everyone has the capability of using the DNS challenge. There must be a better way.
I know this is an old question, but I'm trying to do this (via WAF) and I'm having some issues.
I've added the UTM itself as a real webserver and created a virtual one with HTTPS redirection. However, this doesn't work. Attempting to open the portal URL with HTTP still doesn't work, while the portal with HTTPS works.
