[jira] [Comment Edited] (AMQ-6170) X-Frame-Options are not set for static content

["Christopher L. Shannon (JIRA)" <ji...@apache.org>]

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

Christopher L. Shannon edited comment on AMQ-6170 at 3/16/16 8:01 PM:
----------------------------------------------------------------------

No, in those versions the header is applied in a Servlet filter so any static content will not be protected which is why the notice that went out says to upgrade to 5.13.2.  Fixing older versions like 5.11.x and 5.12.x would require more work than just cherry-picking because the version of Jetty is different.


was (Author: christopher.l.shannon):
No, in those versions the header applied in a Servlet filter so any static content will not be protected which is why the notice that went out says to upgrade to 5.13.2.  Fixing older versions like 5.11.x and 5.12.x would require more work than just cherry-picking because the version of Jetty is different.

> X-Frame-Options are not set for static content
> ----------------------------------------------
>
>                 Key: AMQ-6170
>                 URL: https://issues.apache.org/jira/browse/AMQ-6170
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.12.2, 5.11.4, 5.13.1
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>             Fix For: 5.14.0, 5.13.2
>
>
> In AMQ-6113, The X-Frame-Options header was added to the web console.  Unfortunately that patch isn't quite correct because static content is still missing this header.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)