Allow custom configuration for HSTS settings
Description of problem:
Foreman/Satellite currently unconditionally sets the HSTS header to "Strict-Transport-Security: max-age=631152000; includeSubdomains", see https://github.com/theforeman/foreman/blob/develop/config/initializers/secure_headers.rb
While generally a good idea, HSTS has the issue that browsers will refuse to talk unencrypted to the Satellite at all after seeing the HSTS header once.
However, we want /pub/ and /pulp/repos/…/custom/ to be available via HTTP too.
This is not a problem for yum/dnf/wget/curl, as those neither implement nor ever see the HSTS header from Foreman, but regular users quite often want to browse the repos with their browsers and that is not possible with HSTS on (as /pulp/repos/ requires a client cert from the Katello CA when accessed via HTTPS).
As HSTS works based on domains/hostnames, you cannot exclude /pub/ and /pulp/repos/ from it.
The best solution that comes into my mind would be allowing to disable and/or change the HSTS settings, so that the users at least can decide if they want HSTS or not (but still leave it on by default).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. curl -I https://sat.example.com
Strict-Transport-Security: max-age=631152000; includeSubdomains
Depending on the settings
The error you see in Firefox is:
An error occurred during a connection to sat.example.com. SSL peer was unable to negotiate an acceptable set of security parameters. Error code: SSL_ERROR_HANDSHAKE_FAILURE_ALERT
The error you see in Chrome is:
This site can’t provide a secure connection sat.example.com didn’t accept your login certificate, or one may not have been provided.
Try contacting the system admin.
Fixes #22165 - Allow disabling HSTS header
If a user browses to the Foreman server using HTTPS, HSTS headers will
prevent the browser from connecting to the server again using HTTP. This
adds a setting that allows disabling this header for users requiring
browser access to the server.