The ‘ERR_BLOCKED_BY_RESPONSE’ error occurs when response is delivered along with requirements from Chromium such as ‘X-Frame-Options’ and ‘Content-Security-Policy’ aren’t met. It is speculated that Salesforce is setting HTTP headers that are blocking an action that Scoutbees is trying to do, likely due to Javascript running on the page not sourced from a Salesforce-approved location.
Read the entire ‘What Does the ‘ERR_BLOCKED_BY_RESPONSE’ Error Mean?’ thread below:
what dose the error ‘ERR_BLOCKED_BY_RESPONSE ‘ mean?
From Chromium:
> The request failed because the response was delivered along with requirements which are not met (‘X-Frame-Options’ and ‘Content-Security-Policy’ ancestor checks and ‘Cross-Origin-Resource-Policy’ for instance).
No. I don’t think that helps you solve the problem.
If I had to guess. Salesforce sets HTTP headers that block something Scoutbees tries to do. More than likely due to Javascript running in the page that isn’t sourced from a Salesforce approved location
Continue reading and comment on the thread ‘What Does the ‘ERR_BLOCKED_BY_RESPONSE’ Error Mean?’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops, ControlUp Synthetic Monitoring