has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource- ( continue issue from previous post)
has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource- ( continue issue from previous post)
I don't need to see the details, you can just tell me it worked. The reason being is that when you post secure comments I cannot reply directly to them and the threads get difficult to manage.
We have made some changes recently to our CORs handling, and that may be impacting the request you are making from the browser. I will look into this, but it is going to take a few days. I would recommend not making the calls directly from the browser if possible (delegate them to your server).
HI We found the Issue: if we have a / behind the CORS domain link then won't work. So We just remove it. now it works perfectly. thanks.
I was going to mention that, but I wasn't sure. Did you recently add the trailing / or did you always have it? If you always had it, we should log that as a bug on our side.
1 Person is following this question.