ERR_BLOCKED_BY_RESPONSE
The content loaded, but its own security headers say it may not be shown here, for example embedded in another page. Chrome obeyed and blocked it.
Quick checks
- Is the content embedded in another page (a frame)? Open it in its own tab instead.
- Try with extensions disabled.
Fixes on Mac
Open the content directly
- Right-click the frame or link and open it in a new tab; the block only applies to embedding.
Disable extensions that modify headers
- Test in a private window; disable header- or privacy-modifying extensions.
Fixes on Windows
Same as Mac
- Open the content directly and test without extensions.
Other devices
Apps
- Inside apps that embed web pages, update the app; the embedded site may have changed its rules.
Still not working?
Developers: the response carries a header that forbids this use:
X-Frame-Options: DENY/SAMEORIGINorContent-Security-Policy: frame-ancestors …block framing.Cross-Origin-Resource-Policy: same-originblocks loading the resource from other sites.Cross-Origin-Embedder-Policy: require-corpon the embedding page requires every resource to opt in.
Check the failing request in DevTools › Network. Adjust the header on the resource you control, or don't embed content whose owner forbids it.
See what’s happening
LightAtom's connections view confirms the browser reached the server, which tells you the block is a header, not a network problem.
Frequently asked questions
What does ERR_BLOCKED_BY_RESPONSE mean?
The server answered, but its headers forbid using the response in this context, such as inside an iframe on another site. Chrome enforces that.
Why does a site refuse to load in an iframe?
X-Frame-Options or a CSP frame-ancestors rule prevents framing, to protect against clickjacking. Only the site's owner can allow it.
Is ERR_BLOCKED_BY_RESPONSE a network problem?
No. The connection worked; a security policy blocked the content.