[
https://issues.apache.org/jira/browse/WW-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178735#comment-17178735
]
ASF subversion and git services commented on WW-5085:
-----------------------------------------------------
Commit 889601522878c8fd81493e79b5d47778f41f0e67 in struts's branch
refs/heads/master from Lukasz Lenart
[ https://gitbox.apache.org/repos/asf?p=struts.git;h=8896015 ]
Merge pull request #432 from salcho/coop-coep-post
WW-5085: Add Cross-Origin Opener Policy (COOP) and Cross-Origin Embedder Policy
(COEP) support
> Add Cross-Origin Opener Policy and Cross-Origin Embedder Policy Support
> -----------------------------------------------------------------------
>
> Key: WW-5085
> URL: https://issues.apache.org/jira/browse/WW-5085
> Project: Struts 2
> Issue Type: New Feature
> Components: Core Interceptors
> Affects Versions: 2.6
> Reporter: Giannis Chatziveroglou
> Priority: Major
> Fix For: 2.6
>
> Original Estimate: 72h
> Time Spent: 50m
> Remaining Estimate: 71h 10m
>
> We would like to add support in Struts for Cross-Origin Opener and
> Cross-Origin Embedder Policy.
> COOP is a security mitigation that lets developers isolate their resources
> against side-channel attacks and information leaks. COOP is now supported by
> all major browsers.
> A COOP interceptor will be implemented to add COOP headers to HTTP responses,
> allowing developers to configure COOP to use {{unsafe-none}}, {{same-site}}
> or {{same-origin}}. Finally, developers will be able to disable COOP entirely
> for a set of exempted paths that are intended to be used cross-site.
>
> COEP is a security mitigation which lets developers ensure that all resources
> loaded by a given document have explicitly opted into being embedded. COEP is
> now supported by all major browsers.
> A COEP interceptor will be implemented to add COEP headers to HTTP responses,
> configuring COEP to the only accepted value "require-corp". A built-in
> handler for COEP violation reports that will be used to collect and provide
> textual explanations of these reports. This will be achieved with the setting
> of the "report-to" header to a default endpoint or one specified by the
> developer.
> Additionally, developers will be able to choose between two options: whether
> they want to both block resources and send report to the endpoint or only
> send a report without blocking the resources. Finally, developers will be
> able to disable COEP entirely.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
