$http error callback doesn't have xhr.statusText

[phillycoder]

There is no way to get XHR statusText in $http error callback. Currently this only returns status(number - statusCode).

It would be really helpful to get status text to display the server error message in the browser.

Like examples,
404 - Resource not found
400 - User ID already exists

[danbarua]

+1 Just ran into this.

[phillycoder]

@jimlyndon thx for the fix, i hope your pull request will be accepted.

[danbarua]

@jimlyndon thank you!

[jimlyndon]

No prob. I have a story on the wall waiting for this fix as well. So we'll see :)

[phillycoder]

Hi Guys, Anyone know if this is fixed in the trunk?

[protoze]

We're working with another team's backend that we don't really have control over and it would be really nice if we could leverage that system's existing error messages by using the status text.

[jimlyndon]

The PR mentioned above hasn't been pulled, and I don't know if the fix has
been satisfied by another, as I haven't heard back from anyone on the PR
and have been off the grid w other projects.

But it's an easy fix and super useful. Feel free to comment on the PR
thread also.
On Jun 15, 2013 3:58 PM, "protoze" [email protected] wrote:

We're working with another team's backend that we don't really have
control over and it would be really nice if we could leverage that system's
existing error messages by using the status text.

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

[markbarton]

Yep just hit this issue as well = hopefully will be rolled in soon.

[mikeobrien]

Ug, same here, need this. 👍

[adamspe]

+1

[ferconsigli]

Same here, we also need to get the status text of the responses.

[Darmikon]

statusText is very important, please add it to response

[acollard]

+1

[welsh-dwarf]

+1, just hit this.

[iSchlicht]

+1

[tamalnath]

I faced the same problem on version 1.2.24

[petebacondarwin]

Is this not available in 1.2.24: See 32c09c1

[owen26]

same problem on version 1.3.0

for a temporary solution for myself, changed source code as the following:

promise.success = function(fn) {
    promise.then(function(response) {
      fn(response.data, response.status, response.headers, config, response.statusText);
    });
    return promise;
  };

  promise.error = function(fn) {
    promise.then(null, function(response) {
      fn(response.data, response.status, response.headers, config, response.statusText);
    });
    return promise;
  };

[caitp]

@owen26 we probably arent going to extend those in core because if we ever want to add more it just gets really sucky. why not just use .then() for it?

[tamalnath]

At least it should be documented somewhere saying statusText will only be available in .then() and not in .success()/.error().

[OzBob]

here's the work around to get StatusText (as pointed out that some moblie browsers strip out DATA from successfull responses: http://stackoverflow.com/a/28470163/1586498

[oyevtushok]

Not sure if it'll work for everyone, but you can use then/catch. First argument of catch contains both statusText and status(which is response code) properties

[stefanofornari]

+1 to get this fixed