You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Larry McCay (JIRA)" <ji...@apache.org> on 2017/09/01 12:41:00 UTC

[jira] [Commented] (KNOX-1017) Add support for enabling "Strict-Transport-Security" header in Knox responses

    [ https://issues.apache.org/jira/browse/KNOX-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150445#comment-16150445 ] 

Larry McCay commented on KNOX-1017:
-----------------------------------

[~lappanna] - thank you for filing this and indicating that you will provide a patch!
I have added you as a contributor and assigned this JIRA to you.
Look forward to your contribution.

If you have any questions on the WebAppSec provider just give a shout.


>  Add support for enabling "Strict-Transport-Security" header in Knox responses 
> -------------------------------------------------------------------------------
>
>                 Key: KNOX-1017
>                 URL: https://issues.apache.org/jira/browse/KNOX-1017
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Latha  Appanna
>            Assignee: Latha  Appanna
>              Labels: headers
>             Fix For: 0.14.0
>
>
> The HTTP Strict-Transport-Security response header is a security feature that lets a web site tell browsers that it should only be communicated with using HTTPS, instead of using HTTP. Possible values are:
>  
> *  max-age=<expire-time>
> *  max-age=<expire-time>; includeSubDomains
> *  max-age=<expire-time>; preload



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)