Cross-Origin-Resource-Policy
Lets a resource state which origins or sites may embed it without CORS.
Support in current browsers
Checked against the current browser versions recorded in MDN browser data 8.0.7.
| Browser | Minimum | Outcome | Reason |
|---|---|---|---|
| Chrome | 150 | Works with limits | Every required mapped feature is available, but BCD records one or more qualifications. |
| Edge | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Firefox | 152 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Safari | 26.5 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Chrome for Android | 150 | Works with limits | Every required mapped feature is available, but BCD records one or more qualifications. |
| Firefox for Android | 152 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Safari on iOS | 26.5 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Android WebView | 150 | Works with limits | Every required mapped feature is available, but BCD records one or more qualifications. |
| Samsung Internet | 29.0 | Works | Every required mapped BCD feature is available without a recorded qualification. |
What this feature can and cannot do
Helps protect against
- Cross-origin resource inclusion
- Selected speculative side-channel exposure
Does not guarantee
- Authorised CORS reads
- Application authorisation
- Resources served without the header
What you need before using it
- An accurate resource-sharing model
Fallback to keep in place
Use authentication, CORS, and response minimization appropriate to each resource.