Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.7.3
Description
Updating the below configurations does not take affect in Ambari 2.7.x version
http.strict-transport-security=max-age=0 views.http.strict-transport-security=max-age=0
After setting the above configurations still API response gives below max-age headers.
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
I see AmbariServerSecurityHeaderFilter.java setting the correctly defined params but later somehow it is going to default value.
This works fine in 2.6.x versions.