Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CORS - Using my own local copy, cannot access deweyapp.com resources #163

Open
cpsubrian opened this issue Feb 17, 2017 · 2 comments
Open

Comments

@cpsubrian
Copy link

Totally fine if this is a 'wont fix', but I'd like to run my own local copy of the app, because there is some custom styling that I'd like to apply. The local app boots up fine but I can't access any of the resources stored on the server (such as favicons) because of CORS headers. I get why they are there. Not sure of a 'simple' solution off hand.

@jtnegrotto
Copy link

jtnegrotto commented Apr 3, 2017

I'm having the same issue with the extension from the chrome webstore.

@arendtio
Copy link

arendtio commented Sep 1, 2017

Well, actually that breaks a lot of things for me. I did a fresh install from the chrome store and have neither screenshots nor favicons. The console has lots of origin related errors:

Access to Image at 'https://deweyapp.com/screenshot/https%3A%2F%2Ffeathericons.com%2F/screenshot.png' from origin 'chrome-extension://aahpfefkmihhdabllidnlipghcjgpkdm' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'chrome-extension://aahpfefkmihhdabllidnlipghcjgpkdm' is therefore not allowed access. The response had HTTP status code 521.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants