Angularjs 1.1.5 doesn't work for me

[ndemoreau]

Just to let you know. I didn't have time to investigate but I think it's linked to angular-resource.

It loads but not my data.

[NickClark]

I think your issue may be due to this commit: angular/angular.js#1004

As it says in the commit, just add this to your module:

myAppModule.config(['$httpProvider', function($httpProvider) {
    $httpProvider.defaults.headers.common["X-Requested-With"] = 'XMLHttpRequest';
}]);

[hiravgandhi]

@ndemoreau - Let me know if @NickClark's solution fixes your issues.

[gwright]

I just spent some time digging into Angular and Rails to really understand this issue as it relates to $resource in a Rails environment.

It turns out that Rails is a bit cagey about utilizing the Accepts header from an HTTP request. It has to have the X-Requested-With header or it has to look like a request from something other than a browser, which means it can't have a wildcard mime type */*. Earlier versions of Angular sent the X-Requested-With header so the wildcard mime type didn't matter but, without that header, Rails thinks it is talking to a browser since $resource sends an Accept header of application/json, text/plain, */*.

So an alternative to adding the X-Requested-With header is to be more specific about what you are requesting. In my case instead of changing all the HTTP requests generated by $http, I just changed the requests generated by my use of $resource:

  App.factory('Record', function($resource) {
    return $resource("/records/:id", {
      id: "@id"
    }, {
      update: {
        method: "PUT"
      },
      query: {
        isArray: true,
        method: "GET",
        headers: {
          "Accept": "application/json",
          "X-Requested-With": "XMLHttpRequest"
        }
      }
    });
  });

[eddiemonge]

@gwright wont that only work for query requests so all your other requests will fail?

[gwright]

@eddiemonge I haven't looked at this in a while but generally the other types of requests (PUT, POST, DELETE) have an empty body and so the format of an empty response is somewhat irrelevant. In those cases it is the status code that is of interest.

So perhaps it would be more correct send an explicit accepts header on all types of HTTP requests. Sending X-Requested-With is still problematic with respect to CORS process though, as I understand it.

[NickClark]

Sounds like several solutions have been provided. Also this isn't an issue with angularjs-rails, so can this be closed? 👍

[hiravgandhi]

Closing this issues.