Technically CORS are not failing because of the vendor but because of your local application.
Two things that come in to my mind: 1. use firefox 2. Run chrome with --disable-web-security parameter. Sent from my iPhone > On 10/lug/2014, at 21:41, Dane Vinson <[email protected]> wrote: > > My Angular app is making a get request to an external source. The developer > console in Chrome (and in IE) is showing "No 'Access-Control-Allow-Origin' > header is present on the requested resource.", the result of the request is > error and the promise's .error is showing a data argument which is empty. The > error seems to indicate that the host service isn't set up for CORS but I > have a hard time believing that as it's a national vendor who takes this sort > of request routinely. Further, Fiddler is showing a response code of 200 for > the request and the return data is exactly what I expect, no indication of > any error. It seems quite odd that $http's get is returning error but Fiddler > is showing a 200. > > Any help you may provide will be appreciated. > > Thanks > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
