struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giannis Chatziveroglou (Jira)" <j...@apache.org>
Subject [jira] [Updated] (WW-5085) Add Cross-Origin Opener Policy and Cross-Origin Embedder Policy Support
Date Mon, 03 Aug 2020 11:20:00 GMT

     [ https://issues.apache.org/jira/browse/WW-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Giannis Chatziveroglou updated WW-5085:
---------------------------------------
    Description: 
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 request cycle listener 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.

  was:
We would like to add support in Struts for Cross-Origin Opener and Cross-Origin Embedder
Policy.

COOP is a security mitigation that offers developers window-level isolation and prevents
other websites from directly interacting with the application window. COOP is now supported
by all major browsers.

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 COOP interceptor will be implemented 

 

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.


> 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
>  Remaining Estimate: 72h
>
> 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 request cycle listener 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)

Mime
View raw message