What's the right way to make a $http call that can be resolved in ui-router with TypeScript?

Question

I've got a simple HTTP service that I hit via a service;

module shared {

    export interface IAuthService {
        isAuthenticated: () => any;
    }

    export class AuthService implements IAuthService {
        static $inject = ['$http'];

        constructor(private $http:ng.IHttpService) {
        }

        isAuthenticated():any {
            return this.$http({
                method: 'GET',
                url: 'http://localhost/auth'
            });
        }
    }

    export var app:ng.IModule = app || angular.module('shared', ['ngResource']);
    app.service('AuthService', AuthService);
}

And I use it in a route resolve;

$stateProvider.state('app', {
            url: "/app",
            abstract: true,
            templateUrl: "app/menu.html",
            controller: 'AppController',
            resolve: {
                authService: 'AuthService',
                isAuthenticated: function (authService) {
                    return authService.isAuthenticated();
                }
            }
        });

The problem is, I use HTTP response codes for the result -- if the user is authenticated, I send back some JSON data (hence the any return type until I build the class). If not, I return HTTP/403.

This worked ok in JS, perhaps by coincidence, but it seems in migrating to typescript, the 403 now stops the resolve dead in its tracks and the app just sits there.. Has anyone come across this? Is there a more correct approach?

EDIT: I was asked for the JS that's generated -- the .state is identical, the service gets converted into this;

AuthService.prototype.isAuthenticated = function () {
                return this.$http({
                    method: 'GET',
                    url: this.ConfigService.apiBaseUri + '/authentication/authenticated',
                    headers: { 'Authorization': this.ConfigService.sessionId }
                });
            };

Answer 1

So the answer turns out to be pretty obvious in retrospect.. A rejected promise rejects the state transition as well. So the correct solution when there might be a failure of a $http call that should proceed anyway, is to add a .then(function(data) {//...},function() {//...}) to the call inside the resolve method. In my case;

isAuthenticated: function (authService) {
    return authService.isAuthenticated().then(function(data) { return data; }, function() { return null; });
}