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 support #273

Open
Eweol opened this issue Sep 19, 2019 · 3 comments
Open

CORS support #273

Eweol opened this issue Sep 19, 2019 · 3 comments

Comments

@Eweol
Copy link

Eweol commented Sep 19, 2019

I want to write a FE for my own in .Net-Core Blazor for my ZWay.
I started to implement the authorization and get the Console Error on ClientSide

Access to fetch at 'http://XXX.XXX.XXX.X:YYYY/ZAutomation/api/v1/login' from origin 'http://localhost:YYYY' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.

So is there a chance to set an Origion on ZWay-Server side to don't have a wildcard origion?

@PoltoS
Copy link
Member

PoltoS commented Sep 20, 2019

Do you want a field to be filled by you somewhere?

BTW, why Chrome is not accepting * anymore?

@Eweol
Copy link
Author

Eweol commented Sep 21, 2019

Hey @PoltoS ,
A field or maybe a Env-Variable or a config-file entry or something like that

I don't even know since when it's not allowed but I also rode here on Microsoft Doc's that it isn't allowed anymore.

@PoltoS
Copy link
Member

PoltoS commented Sep 21, 2019

I don't see where * is explicitelly disallowed. If it is an individual proble, you can change it in the code of the automation/ (search for Access-Control-Allow-Origin). If it becomes major problem, we will analyse it to understand how to workaround it correctly.

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