You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: