大网数据广告活动
Web 标准与前端开发

Cross-Origin-Embedder-Policy-Report-Only (COEP) header

· 52CE 我爱测

The HTTP **`Cross-Origin-Embedder-Policy-Report-Only`** (COEP) response header configures the current document's _report-only_ policy for loading and embedding cross-origin resources that are requested in `no-cors` mode.

The HTTP Cross-Origin-Embedder-Policy-Report-Only (COEP) response header configures the current document's report-only policy for loading and embedding cross-origin resources that are requested in no-cors mode.

The header allows website administrators to report on resources that would be blocked by Cross-Origin-Embedder-Policy, without preventing them from being loaded. This allows for a softer rollout of enforcement.

Violations of the policy may be reported using the Reporting API. Reports can be observed in the page for which the policy is being set using a ReportingObserver, and sent to server endpoints defined in a Reporting-Endpoints HTTP response header, and selected using the report-to parameter. For more information see COEPViolationReport.

<table class="properties"> <tbody> <tr> <th scope="row">Header type</th> <td>Response header</td> </tr> </tbody> </table>

Syntax

Cross-Origin-Embedder-Policy-Report-Only: <token>; <parameter>

Directives

The header should only be set with just one token and a report-to endpoint.

Setting the header more than once or with multiple tokens is equivalent to setting unsafe-none. Omitting report-to makes the header functionally inert.

The <token> value can be one of:

  • unsafe-none

    • : Allows the document to load cross-origin resources requested in no-cors mode without giving explicit permission through the Cross-Origin-Resource-Policy header. This is the default value.
  • require-corp

    • : A document can only load resources requested in no-cors mode from the same origin, or resources that have explicitly set the Cross-Origin-Resource-Policy header to a value that allows it to be embedded.

      Cross-origin resource loading will be blocked by COEP unless:

      • The resource is requested in no-cors mode and the response includes a Cross-Origin-Resource-Policy header that allows it to be loaded into the document origin.
      • The resource is requested in cors mode; for example, in HTML using the crossorigin attribute, or in JavaScript by making a request with {mode="cors"}. Note that requests made in cors mode won't be blocked by COEP or trigger COEP violations, but must still be permitted by CORS.
  • credentialless

    • : A document can load cross-origin resources that are requested in no-cors mode without an explicit permission via the Cross-Origin-Resource-Policy header. In this case requests are sent without credentials: cookies are omitted in the request, and ignored in the response.

      The cross-origin loading behavior for other request modes is the same as for require-corp. For example, a cross-origin resource requested in cors mode must support (and be permitted by) CORS.

The <parameter> is optional, and can be one of:

  • report-to <endpoint_name>
    • : The <endpoint_name> is the name of the endpoint to which policy violations will be sent. The mapping between the name and a particular endpoint is defined separately in the Reporting-Endpoints HTTP header.

Specifications

Browser compatibility

See also

来源:MDN Web Docs / Mozilla 贡献者 · 作者与贡献记录 · CC BY-SA 2.5。离线整理了版式、链接和媒体显示。

资料来源与适用范围

资料来源
MDN Web Docs / Mozilla 贡献者
适用范围
请按文中版本与环境说明核对
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 2.5

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。