[
https://issues.apache.org/jira/browse/AMBARI-25159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777195#comment-16777195
]
Hudson commented on AMBARI-25159:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #431 (See
[https://builds.apache.org/job/Ambari-branch-2.7/431/])
AMBARI-25159. http.strict-transport-security change does not take affect
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=63be8e20dac7d66a35ea4714e46086631644a388])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
> http.strict-transport-security change does not take affect in 2.7.x
> -------------------------------------------------------------------
>
> Key: AMBARI-25159
> URL: https://issues.apache.org/jira/browse/AMBARI-25159
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.3
> Reporter: amarnath reddy pappu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Updating the below configurations does not take affect in Ambari 2.7.x version
> {noformat}
> http.strict-transport-security=max-age=0
> views.http.strict-transport-security=max-age=0
> {noformat}
> After setting the above configurations still API response gives below max-age
> headers.
> {noformat}
> Strict-Transport-Security: max-age=31536000 ; includeSubDomains
> {noformat}
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
