Skip to content

bug: Access to script at been blocked by CORS policy #26

Description

@dep

Describe your issue?

I've seen this issue working locally with the Requestly extension in Chrome.

Access to script at been blocked by CORS policy. Permission was denied for this request to access http://localhost/reportinglocalhost.js redirected from https://djm113gw5h5.cloudfront.net/assets/reporting.js) from origin https://ww.<my-site>.net

It's almost as if Chromium is tightening up this rule somehow.

For what it's worth I can circumvent it by launching chrome like this, but it feels wrong:

open -na "Google Chrome" --args \
  --user-data-dir="/tmp/chrome-dev" \
  --disable-web-security \
  --disable-site-isolation-trials

Repro steps

  1. Use Requestly in Chrome
  2. Set up a redirect rule
  3. Reload

What Requestly tool were you using?

  • Extension
  • Desktop-App
  • Android SDK
  • Selenium

Your Environment

latest

Requestly Version

latest

Error screenshot

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions