Cross-Origin Resource Policy (CORP)
On this page
Cross-Origin Resource Policy (CORP)
Cross-Origin Resource Policy is a policy set by the Cross-Origin-Resource-Policy
HTTP header that lets websites and applications opt in to protection against certain requests from other origins (such as those issued with elements like <script>
and <img>
), to mitigate speculative side-channel attacks, like Spectre, as well as Cross-Site Script Inclusion attacks.
CORP is an additional layer of protection beyond the default same-origin policy. Cross-Origin Resource Policy complements Cross-Origin Read Blocking (CORB), which is a mechanism to prevent some cross-origin reads by default.
Caution
As this policy is expressed via a response header, the actual request is not prevented. Rather, the browser prevents the result from being leaked by stripping the response body.
Summary
You can think of CORP as similar to CORS but specifically tailored for <script>
and <img>
elements. It allows you to decide whether your resources can be loaded based on criteria such as same-site
, same-origin
, or cross-origin
.
Usage
Cross-Origin-Resource-Policy: same-site
: Only requests from the same Site can read the resource.Cross-Origin-Resource-Policy: same-origin
: Only requests from the same origin (i.e. scheme + host + port) can read the resource.Cross-Origin-Resource-Policy: cross-origin
: Requests from any origin (both same-site and cross-site) can read the resource.
Example
In the provided example, the script profile.js
will only load if both the client and server originate from the same site. For instance, if the client’s origin is app.example.com
, the script will load successfully. However, if the client comes from a different site, such as app.anothersite.com
, the script will not load.
Client source code:
Server (e.g. CDN) source code: