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 is blocking the Web Config (V1, V2) #523

Closed
Camaendir opened this issue May 23, 2018 · 5 comments
Closed

CORS is blocking the Web Config (V1, V2) #523

Camaendir opened this issue May 23, 2018 · 5 comments

Comments

@Camaendir
Copy link

Camaendir commented May 23, 2018

In every Browser on Windows 10 (I tried Chrome, Firefox, Firefox Nightly, IE, Edge) the first request fails due to the "Access-Control-Allow-Origin" Header missing. Every Browser outputs something like this:
"
Failed to load http://homie.config/heart: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://marvinroger.github.io' is therefore not allowed access
"
I am using the v1 Version of the Web Configurator

@Camaendir Camaendir changed the title CORS is blocking the Web Config CORS is blocking the Web Config (V1) May 23, 2018
@timpur
Copy link
Contributor

timpur commented May 23, 2018

Have you tried the latest releases of homie. If that doesn't work try development of homie

see #446, this should be fixed

@Camaendir Camaendir changed the title CORS is blocking the Web Config (V1) CORS is blocking the Web Config (V1, V2) May 24, 2018
@Camaendir
Copy link
Author

@timpur

Have` you tried the latest releases of homie. If that doesn't work try development of homie see #446, this should be fixed

I tried the latest Versions now (2.0.0, 2.1). It still doesn't work. The Browser is giving me the same response every time.

@timpur
Copy link
Contributor

timpur commented May 24, 2018

Okay, I'll have a look tomorrow

@Camaendir
Copy link
Author

@timpur
Thanks again for helping. I deleted and reinstalled everything and now it works. I still don't know where the Issue was but it works fine now.

@timpur
Copy link
Contributor

timpur commented May 24, 2018

:)

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

2 participants