I am not 100% sure what Google did to Chromium in Update 42. However after that update landed I started to get reports of our Angularjs application started to have problems communicating with our ASP.NET WebAPI. We started getting errors similar to this:
No ‘Access-Control-Allow-Origin’ header is present on the requested resource
You must be logged in to post a comment.