Can only reiterate the earlier comment: "Implementation of this "feature" should not depend on popularity. It is the only right *and* secure way to redirect from non-www to www domain. If this is not done, then the HSTS header is never sent for the non-www version of the domain, allowing MITM attacks / stripping HTTPS.

"

Implementation of this "feature" should not depend on popularity. It is the only right *and* secure way to redirect from non-www to www domain. If this is not done, then the HSTS header is never sent for the non-www version of the domain, allowing MITM attacks / stripping HTTPS.

IMHO Plesk should use the secure way by default: redirect from HTTP to HTTPS first (allowing the HSTS header to be sent) and *then redirect from non-www to www.

If there really are people who wish to not do this, avoid one redirect and immediately redirect to https://www.domain.tld, then allow them to override the secure default. IMHO this is over-optimization, as these days (with HTTP/2) there is not nearly as much overhead as there was before.

Please fix this if this is not done already. :-)

When in Hosting Settings setting the Preferred Domain to anything but "None" and enabling "Permanent SEO-safe 301 redirect from HTTP to HTTPS" Plesk will redirect every request in one go.

For example, I configure my domain to redirect HTTP to HTTPS and to prefer the absence of "www". When I now request "http://www.example.com/" it will be redirected to "https://example.com/" in one single redirect. According to the Dutch Web application guidelines the server should first redirect to HTTPS and only then redirect to either include or exclude the www subdomain. (see attachment, taken from https://en.internet.nl/)

And it also should give the ability to put one year to the max-age var.