Skip to main content

An Overview On Angular Interceptor

In Angular application, the Http request and response can be inspected and transform using the Interceptors. An application can configure multiple interceptors if needed. Each interceptor gets invoked for every Http request.

Interceptor Flow:

The Interceptors moto is to intercepts and handles an 'HttpRequest' or 'HttpResponse'

Most interceptors transform the outgoing request before passing it to the next interceptor in the chain, by calling 'next.handle(request)'. An interceptor may transform the response event stream as well, by applying addition RXJS operators on the stream returned by 'next.handle()'

More rarely, an interceptor may handle the request entirely and compose a new event stream instead of invoking 'next.handle()'. This is acceptable behavior, but keep in mind that further interceptors will be skipped entirely.

It is also rare but valid for an interceptor to return multiple responses on the event stream for a single request.


  • Let's suppose consider we have 2 interceptors in our application. Once the application starts to call an API, our Http request enters the 1st interceptor there we will implement the most common logics like adding a custom header, adding access token, etc.
  • After that 'next.handle()'(next is HttpRequest Handler) will pass our Http request to the 2nd interceptor, then our Http request executes the logic in 2nd interceptor like the 1st one. 
  • In 2nd interceptor 'next.handle()' method executes since it is last interceptor request will be sent to the API. 
  • Now API response first will be captured by 2nd interceptor, here we can implement some common logics like filtering response or retry call for API if it fails, etc. after that Http response will enter to 1st interceptor will be processed similar way as in 2nd interceptor. 
  • Finally, the response will be captured by services  and the components

Create A Sample Angular App:

Let's understand interceptor features by implementing it in a sample angular application.

Command To Install Angular CLI:(If not installed on your system previously)

npm install -g @angular/cli
Angular CLI Command To Create Angular App:

ng new your_project_name
Command To Run App:

ng serve
Let's create a service that triggers an Http get request.
src/app/app.service.ts:
import { Injectable } from '@angular/core';
import { HttpClient } from '@angular/common/http';

@Injectable()
export class AppService {
  constructor(private httpClient: HttpClient) {}

  get(){
      this.httpClient.get("http://test.com/api")
      .subscribe(
          (response) => {console.log('success')},
          (error) => {console.log('fails')}
      )
  }
}
Here created a test angular service it helps to understand interceptors better way. The API used here is a dummy one.

Now inject the HttpClient and our service in the AppModule file.
src/app/app.module.ts:
import { HttpClientModule } from '@angular/common/http';

import { AppService } from './app.service';
// some code hidden for better display
@NgModule({
  imports: [HttpClientModule],
  providers: [AppService]
})
export class AppModule {}
  • (Line: 7) HttpClientModule imported which is available at '@angular/common/http'
  • (Line: 8) imported our 'AppService'
Now, let's add a button that triggers our dummy API.
src/app/app.component.ts:
import { Component } from '@angular/core';

import { AppService } from './app.service';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
})
export class AppComponent {
  title = 'demo-interceptor';

  constructor(private appSerive:AppService){

  }
  triggerService(){
    this.appSerive.get();
  }
}
  • Injected our 'AppService' into our component.
src/app/app.component.html:
<div>
  <input type="button" value="Trigger Service" (click)="triggerService()">
</div>

Create A Test1Interceptor:

Let's create our first interceptor which is a dummy one does nothing with 2 console logs to track execution.
src/app/test1.interceptor.ts:
import { Injectable } from '@angular/core';
import {
  HttpInterceptor,
  HttpRequest,
  HttpHandler,
  HttpEvent,
} from '@angular/common/http';
import { Observable } from 'rxjs';

@Injectable()
export class Test1Interceptor implements HttpInterceptor {
  intercept(req: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> {
    console.log('here request can modify -- Interceptor 1')
    var handle = next.handle(req);
    console.log('here response can modify -- Interceptor 1')
    return handle;
  }
}
  • (Line: 11) HttpInterceptor is an interface that needs to be implemented by our interceptor class. The 'HttpInterceptor' interface loads from '@angular/common/http'
  • (Line: 12) 'intercept()' is an abstract method from 'HttpInterceptor' that we need to implement for identifying and handling an Http request. The 'req' parameter of type 'HttpRequest<any>' is for outgoing request object to handle. The 'next' parameter of type 'Http' is to trigger the next interceptor in the flow of the chain or the backend(API). If no interceptor remains in the chain, then returns an observable of the event stream.
  • (Line: 13&15) console log to understand interceptor execution.

Import Provider In AppModule:

To use the same instance of 'HttpInterceptor' for the entire application, import the 'HttpClientModule' only in our 'AppModule', and add the interceptors to the root application injector. If we import 'HttpClientModule' multiple times across different modules(for example, in lazy loading modules), each import creates a new copy of the 'HttpClientModule', which overwrites the interceptor provided in the root module.
src/app/app.module.ts:
import { HttpClientModule, HTTP_INTERCEPTORS } from '@angular/common/http';
import { Test1Interceptor } from './test1.interceptor';

@NgModule({
  imports: [HttpClientModule],
  providers: [
    {
      provide: HTTP_INTERCEPTORS,
      useClass: Test1Interceptor,
      multi: true,
    }
  ],
  bootstrap: [AppComponent],
})
export class AppModule {}
  • (Line: 8) The 'HTTP_INTERCEPTORS' is a multi-provider token that represents the array of registered 'HttpInterceptor' objects.
  • (Line: 9) assign our interceptor class.
  • (Line: 10) 'multi' is required to set true, which allows us to have multiple interceptors in our application all will be injected with the help of multi-provider token 'HTTP_INTERCEPTORS'.

Test Interceptors:

Now track our console logs added in our interceptor to understand the flow.

For better understanding lets add one more interceptor as below.
src/app/test2.interceptor.ts:
import { Injectable } from '@angular/core';
import {
  HttpInterceptor,
  HttpRequest,
  HttpHandler,
  HttpEvent,
} from '@angular/common/http';
import { Observable } from 'rxjs';

@Injectable()
export class Test2Interceptor implements HttpInterceptor {
  intercept(req: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> {
    console.log('here request can modify -- interceptor 2')
    var handle = next.handle(req);
    console.log('here response can modify -- intereptor 2')
    return handle;
  }
}
Now inject the Test2Interceptor in AppModule like we did in previous steps.
src/app/app.module.ts:
import { HttpClientModule, HTTP_INTERCEPTORS } from '@angular/common/http';

import { Test1Interceptor } from './test1.interceptor';
import { Test2Interceptor } from './test2.interceptor';


@NgModule({
   providers: [
    {
      provide: HTTP_INTERCEPTORS,
      useClass: Test1Interceptor,
      multi: true,
    },
    {
      provide: HTTP_INTERCEPTORS,
      useClass: Test2Interceptor,
      multi: true,
    }
  ]
})
export class AppModule {}
Now track the console log we can understand how the interceptors chain will execute in request and response.

Order Of Interceptor Execution:

The order of the interceptor's execution will be the same as they injected in the AppModule. So if we want to add or skip the interceptors dynamically then we need to add 'if' conditions inside of the interceptors either to execute or skip the transformation of Http request and Http response.

Transform Request Object:

Interceptors can be used to modify the HttpRequest object. It is not recommended to modify them directly. Even most of the HttpRequest object properties are read-only which means they immutable. But Interceptor meant for the transformation so instead of modifying the original Http request object here we will clone them and implement our transformation to the new request object. Using intercepted we can do things like URL modification(not recommended, only can be used in rare cases based on your application business), setting default headers, request caching, etc.

Let's add some custom headers in our sample interceptors for understanding.
src/app/test1.interceptor.ts:
intercept(req: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> {
	const transformedReq = req.clone({
	  headers: req.headers.set('custom-header-1', 'im Interceptor 1')
	});
	return next.handle(transformedReq);
}
  • (Line: 2) 'req.clone()' method is used to set our custom header
  • (Line: 5) newly created HttpRequest object will be delivered to other interceptors if exist or sends to API.
src/app/test2.interceptors.ts:
intercept(req: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> {
    const transformedReq = req.clone({
        headers: req.headers.set('custom-header-2', 'im Interceptor 2')
    });
    return next.handle(transformedReq);
}

Transform Response Object:

In interceptors, it is possible to modify the response object but it is not all recommended to modify the response.
intercept(req: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> {

	return next.handle(req).pipe(
	  map((response:HttpResponse<any>) => {
		 return response.clone({statusText: "hurray"})
	  })
	);
}

Interceptor Providers index.ts:

An ideal way of exposing bulk number providers is by using a separate container file like index.ts. This approach makes AppModule configurations cleaner.
src/app/interceptors/index.ts:
import { HTTP_INTERCEPTORS } from '@angular/common/http';

import { Test1Interceptor } from '../test1.interceptor';
import { Test2Interceptor } from '../test2.interceptor';

export const interceptorProviders = [
  {
    provide: HTTP_INTERCEPTORS,
    useClass: Test1Interceptor,
    multi: true,
  },
  {
    provide: HTTP_INTERCEPTORS,
    useClass: Test2Interceptor,
    multi: true,
  },
];
Now import this 'interceptorProviders' array into the AppModule
src/app/app.module.ts:
import {interceptorProviders} from './interceptor/index';

@NgModule({
  providers: [
    interceptorProviders
  ]
})
export class AppModule {}

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information on Angular Interceptors. I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:

Comments

Popular posts from this blog

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

.Net5 Web API Managing Files Using Azure Blob Storage

In this article, we are going to understand the different file operations like uploading, reading, downloading, and deleting in .Net5 Web API application using Azure Blob Storage. Azure Blob Storage: Azure blob storage is Microsoft cloud storage. Blob storage can store a massive amount of file data as unstructured data. The unstructured data means not belong to any specific type, which means text or binary data. So something like images or pdf or videos to store in the cloud, then the most recommended is to use the blob store. The key component to creating azure blob storage resource: Storage Account:- A Storage account gives a unique namespace in Azure for all the data we will save. Every object that we store in Azure Storage has an address. The address is nothing but the unique name of our Storage Account name. The combination of the account name and the Azure Storage blob endpoint forms the base address for each object in our Storage account. For example, if our Storage Account is n

.Net5 Web API Redis Cache Using StackExchange.Redis.Extensions.AspNetCore Library

In this article, we are going to explore the integration of Redis cache in .Net5 Web API application using the 'StackExchange.Redis.Exntensions' library. Note:- Microsoft has introduced an 'IDistributedCache' interface in dotnet core which supports different cache stores like In-Memory, Redis, NCache, etc. It is simple and easy to work with  'IDistributedCache', for the Redis store with limited features but if we want more features of the Redis store we can choose to use 'StackExchange.Redis.Extensions'.  Click here for Redis Cache Integration Using IDistributedCache Interface . Overview On StackExchange.Redis.Extnesions Library: The 'StackExchange.Redis.Extension' library extended from the main library 'StackExchange.Redis'. Some of the key features of this library like: Default serialization and deserialization. Easy to save and fetch complex objects. Search key. Multiple Database Access Setup Redis Docker Instance: For this sampl

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route. An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaul

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library  jQuery Validate . In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples. Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio. Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as bel

NestJS File Upload

In this article, we are going to understand the steps to create a file uploading endpoint in the NestJS application. Key Features In NestJS File Upload: Let us know some key features of NestJS file upload before implementing a sample application. FileInterceptor: The 'FileInterceptor' will be decorated on top of the file upload endpoint. This interceptor will read single file data from the form posted to the endpoint. export declare function FilesInterceptor(fieldName: string, localOptions?: MulterOptions): Type<NestInterceptor>; Here we can observe the 'fieldName' first input parameter this value should be a match with our 'name' attribute value on the form file input field. So our interceptor read our files that are attached to the file input field. Another input parameter of 'MulterOptions' that provides configuration like file destination path, customizing file name, etc. FilesInterceptor: The 'FilesInterceptor' will be decorated on t

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload: The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client.  Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file.  Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk.  If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application. Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.   Check the link to use the Visual Studio Code for .NET Core Application . IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files f

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items. The main building block of ion-picker as follows: PickerController PickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker. Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger&quo

.Net Core HttpClient JSON Extension Methods Using System.Net.Http.Json Package

.Net Core 3.0 onwards Microsoft brought up a new package called System.Net.Http.Json. This new package provides JSON extension methods for HttpClient. These JSON extension methods will have a prebuild mechanism for serializing or deserializing response data or payload of HttpClient call. System.Net.Http.Json extension methods that are provided to HttpClient, few of them are mentioned below. GetFromJsonAsync PostAsJsonAsync PutAsJsonAsync ReadFromJsonAsync In this article, we understand System.Net.Http.Json package by implementing the HttpClient samples by with and without JSON extension methods and compare them. Create A .Net Core Web API Sample Application: Let's create a .Net Core sample Web API application, from this application we will consume another Web API by implementing HttpClient calls. We can create a Web API sample application using IDE like Visual Studio 2019(Supports .Net Core 3.0 plus) or  Visual Studio Code . Create A Typed Client: In .Net Core using the Http