Issue Setting HSTS and HTTPS redirect on alias domain

[Shamrock]

Server operating system version

Ubuntu 22.4

Plesk version and microupdate number

18.0.71

Hi,
Is there a way to set HSTS and HTTP/HTTPS redirect options for an alias domain?
The main domain has the options set, however the alias domains seem to ignore or don't work in a similar manner it seems.
It is impossible to set them on the alias domains as the SSL certificate, and associated options, is regulated by the main domain.

 

[trialotto]

@Shamrock

The question

Is there a way to set HSTS and HTTP/HTTPS redirect options for an alias domain?

is rhetorical in the sense that the alias will "point" to the "main domain" and, as such, the config of the main domain is equivalently applying to the alias.


Could you be more elaborate about

The main domain has the options set, however the alias domains seem to ignore or don't work in a similar manner it seems.

and describe what you think is "different" from the main domain?


In short, I am not sure whether there is a question and what the question would be.

In case you need or want to configure a specific domain separately, then you should not opt for a setup as alias.

In case you need or want to configure a specific domain separately AND do a redirect (read: afterwards), then there is that option in Plesk (and it not really necessary to setup individual / specific configuration for the domain that will redirect to a main domain).


Just let us know what you are searching for in terms of "what you want to achieve".


Kind regards....

 

[Shamrock]

@Shamrock

The question



is rhetorical in the sense that the alias will "point" to the "main domain" and, as such, the config of the main domain is equivalently applying to the alias.
Actually its not, both scanning with SSL Labs and internet.nl (available in English) show that HSTS is not available on the alias domain.

At least not with the first answer, 301 response.
Same goes for HTTPS redirect.

Could you be more elaborate about



and describe what you think is "different" from the main domain?
As noted, HSTS is not shown in scans, obviously after the 301 redirect it will be but that's not what is tested for.

Same goes for HTTPS redirect.
So if your premise would be correct that the primary config is applied to the alias domains, at least in these 2 cases, that's not what tests show.

In short, I am not sure whether there is a question and what the question would be.

In case you need or want to configure a specific domain separately, then you should not opt for a setup as alias.

In case you need or want to configure a specific domain separately AND do a redirect (read: afterwards), then there is that option in Plesk (and it not really necessary to setup individual / specific configuration for the domain that will redirect to a main domain).


Just let us know what you are searching for in terms of "what you want to achieve".


Kind regards....

In short, and I know it won't do almost nothing for security and a little for privacy of the connection, making sure that the connection to the alias domains receiving a 301 also properly receive HSTS and possible HTTPS redirect responses.
If as you state that should be happening as the primary is set up this way, it would be interesting to know why that's not the case.

Alias is setup as the same website is shown on both, also the mailboxes fo for the primary domain have the automatic aliases via the 3 alias domains.

HOpe this clarifies.