extension modifies request origin schema from HTTP to HTTPS

Extension enforces in a implicit way the server to switch CORS schema from HTTP to HTTP in the access-control-allow-origin header resulting in behavior below.

The 'Access-Control-Allow-Origin' header has a value 'https://localhost:3000' that is not equal to the supplied origin. Origin 'http://localhost:3000' is therefore not allowed access.

chrome: chrome/69.0.3497.100 ext. version: 2018.9.28

In devtools network tab there are origin and referer displayed correctly with HTTP - see screenshot (RIGHT is extension enabled, LEFT extension disabled)

[dharb]

Hey everyone, so sorry about this! We’re working on a fix now that will go out in our next release. In the meantime, as @davidbeermann said you should be able to temporarily resolve this by adding localhost to your whitelist. You can do this by either navigating to the extension settings page and adding ‘localhost’ to the whitelist, or by toggling the Site Privacy Protection switch in the extension pop up.

Thank you for your patience, we’ll have this resolved just as soon as we can.

[davidbeermann]

I also ran into this issue. I was able to resolve it by toggling the Site Privacy Protection checkbox in the extension window. This added localhost to the whitelist. What is a little confusing though is, that once you add a host to the whitelist, the whole extension window is disabled. In order to remove the host from the whitelist, you have to go through the extension management to get to the extension settings – at least in Chrome.