Your KB needs to update the NGINX HSTS with the always parameter.

Hi all,

Did you see a KB: https://support.plesk.com/hc/en-us/articles/115002234393-How-to-enable-Strict-Transport-Security-HSTS-for-domain-on-a-Linux-or-Windows-servers- ?

I was tempted to copy/paste the solutions given on the forum and here....
Later I noticed I needed to change them as they were giving problems.

One is minor and only involves the testing of the domain by SSLlabs.
It turned out that SSLlabs chokes on websites that need credentials to test HSTS
These sites need the "always" attribute.

The other one is the flag "includeSubDomains".
As most will use this nginx directive server wide and they don't really know for a 100% what their clients are up to, you shouldn't use that flag.
I had a client that was running a plain http-only domain on a subdomain on some other server.
That site stopped working for all clients that previously went to their main site.
IMHO the flag includeSubDomains doesn't add anything extra for the site you're securing.
It limits all the sites of that domain to https.
This may be sensible for 1 specific domain, but most likely not a decision for you to make for ALL your clients.

add_header Strict-Transport-Security 'max-age=15768000' always;

good afternoon
This feature will be very useful since many internet sites like google chrome browser already uses this technology, my vote is to be implemented in plesk.

+1

+1

+1

I'm in favour of this as well. But a quick warning: make sure to remove the 'includeSubDomains' if the domain is being used for the Quick Preview URL.

+1

A very simple feature to implement, yet it's been 3+ years. Having to patch it through HTTP directives.

Great idea, hopefully it will be added to Plesk (12.5 would be great).

+1

This could be added for each subdomain/domain config page, just add a tickbox like the one that allows recirect from http to https.

Thanks!

push

I'm already using HSTS via custom headers and would greatly appreciate a standard, less error-prone way for always using HSTS headers and automatic redirect to HTTPS.

@Marco Marsala: HSTS is a great technique and so far the only promising technique to stop SSL-Stripping attacks, for example in public WiFis.
The reason for big sites not using this is that it can break backwards compatibility in some scenarios, which seem more important to them than the security of their customers.

In my opinion, you would want something like the preferred domain setting so you could set https preferred which would...

- add a 301 redirect to https (in Apache HTTP)
- add the HSTS header (in Apache HTTPS)
- along with corresponding 301 redirect in Nginx

Like...https://www.lloyd-day.me/secure-redirects-in-plesk/
Regards

Lloyd

+1

No big sites, like Facebook, use that header.

+1

what's keeping Plesk so long to implement this?