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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP