Alternative Solution: quick and easy: https://youtu.be/3EWrbFfedrA
In this video I show you How to Solve Javascript Cross Domain issue. I give two solutions. One to use while in development stage and one for your server. Solves this error: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.
Original source
24 responses to “How to Solve Javascript Cross Domain”
Thank you mister.
Thanks man saved my life
Thank you so much 48 hours of time wastage solve, screw you chrome, i still love you though
Javascript-rendered pages?
thank you, very helpful and a lot of people met the problem.
can you share codes?
can you upload the files please ?
Thank u very much to share this vedio……….
Thank you a lot !
aaaam that aaaaam sux aaaam and aaaam totally useless!
how php page will work in extension without any server like xampp, wamp etc.
Thank you so much. I had been stuck for hours.
can I get the files please.. please add those to description.
Thank you very much!
Hi!! First solution I dont belive it work for production, it only solves local test. But what I realize from your video is that you can set header in server file to allow drawing html on any browser. In mi php file on server I include:
header("Access-Control-Allow-Origin: *");
and now I can see html response on any browser. Hope this help!!!
Thanks!!
This video just saved me a lot of extra work, thanks mate!
Thank you for sharing this Information , I tried it and it worked for me in making HTTP calls from Angular js 4 to Java EE. Both front end and back end running on two different ports,It saved my day after seeing a lot of stuff in CORS.
Worked for me. Thanks 🙂
there is no way to solve this without a proxy?
Thanks so much
Thanks
I think you didn't load the data_call.html, instead, you call for data.html. Doesn't work for me for the second part. Anyway, thanks
Hello, really very useful. I have another doubt. In my case I'm the developer of the webservice API and I have an app B that is trying to request a json file form mu API but when I try i receive that error message. What should I do to allow any request? because in my case the API has public content and should be as easy as possible to the users of N other apps get that data
Thanks for pointing out that you need to turn off the chrome extension!