HSTS (RFC6797) HTTP Strict Transport Security 7.x

This app adds the HSTS header (RFC-6797) to https-responses. More information about HSTS (HTTP Strict Transport Security) can be found here:

While it's possible to configure frontend web servers to add this header automatically, this app enables you to conditionally handle anonymous users differently from logged in users: You can configure the timeout for both kinds of users differently, e.g. to totally disable HSTS for anonymous users, while enforcing it for logged in users.

Due to the nature of HSTS, this is browser based: Whenever a user logs on on a specific browser, that browser is forced into https in future, no matter if the user ever logs in again. The assumption is that whatever browser is used to log in to the system, it might be used to log in again. If nobody ever logged in from a certain browser and your site is public, you don't need to force them into https.

If a request is received through https, the header will be sent back. You will need to configure the timeout values in *Control Panel / Portal Settings / General*. The timeout is configured in seconds, i.e. one year (365 days) is equivalent to 31536000 seconds

To deactivate this header, undeploy the plugin (it does nothing but add the header), uncheck the Enabled checkbox in the HSTS configuration or minimize the impact by specifying the max-age as 0.

Note, due to the RFC-6797specification, this can only work properly under the following circumstances:

This feature has been suggested in http://issues.liferay.com/browse/LPS-39213. Due to the nature (manipulating HTTPS response headers) there are no meaningful screenshots available for this application. The images you see is the instance configuration panel.

NOTE: This is a 7.x version of Olaf Kock's original module https://web.liferay.com/marketplace/-/mp/application/27551660