Skip to main content

AngularJS - Handling custom HTTP error codes

In this post we will talk about how we can manage on AngularJS, errors like access forbidden or unauthorized. Also we will see what kind of errors we need to throw from a MVC (WebAPI) application.
First off all, don’t try to manage the response error of each HTTP request. You should register an interceptor to HTTP request and manage there all the HTTP errors. Only custom behavior should be managed manually per request.
In the below example we register an HTTP interceptor that redirect the user to the login page when the user is unauthorized to access to access that resources (is not logged in). If you don’t manage the 401 error on the client side, the default behavior of browsers is to display the popup windows where user needs to insert his credentials (Windows Authentification), even if you have another authentication in parallel (Windows Auth. combined with token base – OWIN for example)
In the case he is not allowed to access that resources we display an alert that notify user about this.
var Services = Services || {};
Services.httpCustomInterceptorService = function ($q, $location) {

    var httpCustomInterceptorServiceFactory = {};   

    var responseError = function (rejection) {
        if (rejection.status == 401) {            
            $location.path('/login');
        }
        if (rejection.status === 403) {
            alert('Forbidden - you are not allowed to access this resource');
        }        
        return $q.reject(rejection);
    }
  
    httpCustomInterceptorServiceFactory.responseError = responseError;

    return httpCustomInterceptorServiceFactory;
};

Services.httpCustomInterceptorService.$inject = ['$q', '$location'];
You can register this interceptor using the fallowing line of code:
$httpProvider.interceptors.push('httpCustomInterceptorService');
This HTTP errors codes can be thrown by an MVC custom attribute for example:
401: throw new HttpResponseException(new HttpResponseMessage(HttpStatusCode.Unauthorized));
403: throw new HttpResponseException(new HttpResponseMessage(HttpStatusCode.Forbidden));

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…