CORS configuration for AngularJS is different than jQuery. It requires an extra bit of manual configuration to better conform to the CORS standard for a request. NB: This is only required for some API servers. (The API server is what matters, not the server hosting the AngularJS app.)

AngularJS app config for CORS

myApp.config(['$httpProvider', function($httpProvider) {

	/*
	 * This just helps IE 8/9 with CORS. See https://github.com/angular/angular.js/issues/934
	 * Use with care - There are side-effects.  See why jQuery won't use it at http://bugs.jquery.com/ticket/8283
	 */
        // $httpProvider.defaults.useXDomain = true;

        /*
         * The 'X-Requested-With' header indicates AJAX, which is not cross-domain/JSONP,
         * so we must remove this header for the browser to process this as CORS /JSONP compatible.
         * jQuery doesn't need any of this manual config for $.ajax() calls simply because it intelligently adds/omits this header as needed.
         *
	 * In angular 1.1.1+ this header is removed by default.
	 * Some servers seem to need it (Rails), some don't allow it (Grails), and others don't care (Python/Tastypie).
	 * This is probably more due to those server implementations being based on older conventions vs. newer CORS standards.
	 */
        delete $httpProvider.defaults.headers.common['X-Requested-With'];

}]);