$http Service Not Calling Error Callback on 400

[lsiv568]

Version: 1.1.4

createNewWall: function(wall, successCallback, errorCallback) {
    return $http.post($rootScope.baseAppsAPI + '/walls', null, {
       params: wall
    }).success(function(data, status) {
       return successCallback.call(this, data);
    }).error(function(data) {
       return errorCallback.call(this, data);
    });
}

I verified that the angular isSuccess function is working correctly. I did this by adding it to the window object and verifying that the below code (placed in my sucess callback ) resulted in the error callback being called.

if (window.isSuccess(status)) {
   return successCallback.call(this, data);
} else {
  return errorCallback.call(this, data);
}

Any idea as to what is causing the issue? Something going wrong with the $http promises not being correctly rejected/resolved?

[rtpm]

I am facing the same problem. The way you closed the issue may mean that I can be doing something wrong etc. Can you please share your solution? Can't find this anywhere.

[lsiv568]

Robert.,

I closed the issue because the problem went away (miraculously) after I
made a few modifications to my service. However, it appears to come back
intermittently. So, I no longer know if it is a problem on my end or a
true problem with angular. If you want, I can reopen the issue and you can
add your problem to it? Does that work for yoU?

On Mon, May 13, 2013 at 9:13 AM, Robert notifications@github.com wrote:

I am facing the same problem. The way you closed the issue may mean that I
can be doing something wrong etc. Can you please share your solution? Can't
find this anywhere.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2609#issuecomment-17810417
.

Respectfully,

Louis W. Sivillo

[lsiv568]

As stated above, I am reopening this issue because it happens intermittently. rtpm, please include your use case/any additional info that may help identify the issue

[lsiv568]

Robert,
Thanks for sending this along.

I had an http interceptor that i wrote for basic auth that was not rejecting the promise on response errors.

[se-panfilov]

Thanks bot of you guys. I had the same problem.

[sinelaw]

+1 happens to me when server returns 401

[hari-s]

+1
Callback function not working while server returns 401 status code.

[timsuchanek]

Any progress on this? Facing the same problem with a 400.

[chmanie]

For me @lsiv568's anwser did the trick. It's kind of weird at first but you have to return a rejected promise manually when you build an error interceptor (source).

.factory('myInterceptor', function($q) {
  return {
    response: function (response) { return response; },
    responseError: function(response) {
      // do stuff or
      return $q.reject(response);
    }
  };
});

[senthil1216]

Facing the same problem with a 400..
But why is the issue closed, is there any specific resolution for this issue?

I'm also facing this problem with error 400. Was this issue resolved? If so, in which version?

[nick-merrill]

I'm encountering the same problem with all >299 errors. I'm using Restangular with a custom response interceptor, but I'm getting the error with the out-of-the-box $http service, with the exception of a CSRF token header. (I tried rejecting the deferred object from within Restangular manually anyway, but as expected that didn't change anything.)