search

Z-Wave-Me / zwave-smarthome

Z-Way Smart Home UI
GNU General Public License v3.0
57 stars 38 forks source link

CORS support #273

Open Eweol opened 5 years ago

Eweol commented 5 years ago

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 commented 5 years ago

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

BTW, why Chrome is not accepting * anymore?

Eweol commented 5 years ago

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 commented 5 years ago

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.