{"id":1741,"date":"2023-06-14T08:37:45","date_gmt":"2023-06-14T08:37:45","guid":{"rendered":"http:\/\/waqar-arshad.com\/?p=1741"},"modified":"2023-08-01T06:59:13","modified_gmt":"2023-08-01T06:59:13","slug":"asp-net-core-middleware","status":"publish","type":"post","link":"http:\/\/waqar-arshad.com\/index.php\/2023\/06\/14\/asp-net-core-middleware\/","title":{"rendered":"Asp.Net Core Middleware"},"content":{"rendered":"
\r\n
\r\n \r\n <\/i>\r\n <\/a>\r\n <\/span>\r\n<\/div>
\r\n \r\n <\/i>\r\n <\/a>\r\n <\/span>\r\n<\/div><\/div>\n

ASP.NET Core – Middleware<\/h1>\n\n\n\n

ASP.NET Core introduced a new concept called Middleware.<\/strong> A middleware is nothing but a component (class) which is executed on every request in ASP.NET Core application. In the classic ASP.NET, HttpHandlers and HttpModules were part of request pipeline. Middleware is similar to HttpHandlers and HttpModules where both needs to be configured and executed in each request.<\/p>\n\n\n\n

Typically, there will be multiple middleware in ASP.NET Core web application. It can be either framework provided middleware, added via NuGet or your own custom middleware. We can set the order of middleware execution in the request pipeline. Each middleware adds or modifies http request and optionally passes control to the next middleware component. The following figure illustrates the execution of middleware components.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/a>ASP.NET Core Middleware<\/p>\n\n\n\n

Middlewares build the request pipeline. The following figure illustrates the ASP.NET Core request processing.<\/p>\n\n\n\n

<\/a>ASP.NET Core Request Processing<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Configure Middleware<\/h2>\n\n\n\n

We can configure middleware in the Configure<\/code> method of the Startup class using IApplicationBuilder<\/code> instance. The following example adds a single middleware using Run method which returns a string “Hello World!” on each request.<\/p>\n\n\n\n

public <\/code>class <\/code>Startup<\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    <\/code>public Startup()<\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
    } <\/code><\/pre>\n\n\n\n
    <\/code>public <\/code>void Configure(<\/code>IApplicationBuilder app, <\/code>IHostingEnvironment env, <\/code>ILoggerFactory loggerFactory)<\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        <\/code>\/\/configure middleware using IApplicationBuilder here..<\/code><\/pre>\n\n\n\n
            <\/code><\/pre>\n\n\n\n
        app.Run(<\/code>async (context) =><\/code><\/pre>\n\n\n\n
        {              <\/code><\/pre>\n\n\n\n
            <\/code>await context.Response.WriteAsync(<\/code>\"Hello World!\");<\/code><\/pre>\n\n\n\n
              <\/code><\/pre>\n\n\n\n
        });<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
        <\/code>\/\/ other code removed for clarity.. <\/code><\/pre>\n\n\n\n
    }<\/code><\/pre>\n\n\n\n
}<\/code><\/pre>\n\n\n\n
In the above example, Run()<\/code> is an extension method on IApplicationBuilder<\/code> instance which adds a terminal middleware to the application’s request pipeline. The above configured middleware returns a response with a string “Hello World!” for each request.<\/p>\n\n\n\n
Understand Run Method<\/h2>\n\n\n\n
We used Run extension method to add middleware. The following is the signature of the Run method:<\/p>\n\n\n\n
Method Signature:<\/p>\n\n\n\n
public static void Run(this IApplicationBuilder app, RequestDelegate handler)<\/pre>\n\n\n\n
The Run method is an extension method on IApplicationBuilder<\/code> and accepts a parameter of RequestDelegate<\/code>. The RequestDelegate<\/code> is a delegate method which handles the request. The following is a RequestDelegate signature.<\/p>\n\n\n\n
Method Signature:<\/p>\n\n\n\n
public delegate Task RequestDelegate(HttpContext context);<\/pre>\n\n\n\n
As you can see above, the Run<\/code> method accepts a method as a parameter whose signature should match with RequestDelegate<\/code>. Therefore, the method should accept the HttpContext<\/code> parameter and return Task<\/code>. So, you can either specify a lambda expression or specify a function in the Run method. The lambda expression specified in the Run method above is similar to the one in the example shown below.<\/p>\n\n\n\n
public <\/code>class <\/code>Startup<\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    <\/code>public Startup()<\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
    } <\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
    <\/code>public <\/code>void Configure(<\/code>IApplicationBuilder app, <\/code>IHostingEnvironment env)<\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
         app.Run(MyMiddleware);<\/code><\/pre>\n\n\n\n
    }<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
    <\/code>private <\/code>Task MyMiddleware(<\/code>HttpContext context) <\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        <\/code>return context.Response.WriteAsync(<\/code>\"Hello World! \");<\/code><\/pre>\n\n\n\n
    }<\/code><\/pre>\n\n\n\n
}<\/code><\/pre>\n\n\n\n
The above MyMiddleware<\/code> function is not asynchronous and so will block the thread till the time it completes the execution. So, make it asynchronous by using async<\/code> and await<\/code> to improve performance and scalability.<\/p>\n\n\n\n
\/\/ other code removed for clarity<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
public <\/code>void Configure(<\/code>IApplicationBuilder app, <\/code>IHostingEnvironment env)<\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
     app.Run(MyMiddleware);<\/code><\/pre>\n\n\n\n
}<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
private <\/code>async <\/code>Task MyMiddleware(<\/code>HttpContext context) <\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    <\/code>await context.Response.WriteAsync(<\/code>\"Hello World! \");<\/code><\/pre>\n\n\n\n
}<\/code><\/pre>\n\n\n\n
Thus, the above code snippet is same as the one below.<\/p>\n\n\n\n
app.Run(<\/code>async context => <\/code>await context.Response.WriteAsync(<\/code>\"Hello World!\") );<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
\/\/or <\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
app.Run(<\/code>async (context) =><\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    <\/code>await context.Response.WriteAsync(<\/code>\"Hello World!\"); <\/code><\/pre>\n\n\n\n
});<\/code><\/pre>\n\n\n\n
So, in this way, we can configure middleware using Run<\/code> method.<\/p>\n\n\n\n
Configure Multiple Middleware<\/h2>\n\n\n\n
Mostly there will be multiple middleware components in ASP.NET Core application which will be executed sequentially. The Run method adds a terminal middleware so it cannot call next middleware as it would be the last middleware in a sequence. The following will always execute the first Run method and will never reach the second Run method.<\/p>\n\n\n\n
public <\/code>void Configure(<\/code>IApplicationBuilder app, <\/code>IHostingEnvironment env)<\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    app.Run(<\/code>async (context) =><\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        <\/code>await context.Response.WriteAsync(<\/code>\"Hello World From 1st Middleware\"); <\/code><\/pre>\n\n\n\n
    });<\/code><\/pre>\n\n\n\n
    <\/code><\/pre>\n\n\n\n
    <\/code>\/\/ the following will never be executed<\/code><\/pre>\n\n\n\n
    app.Run(<\/code>async (context) =><\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        <\/code>await context.Response.WriteAsync(<\/code>\"Hello World From 2nd Middleware\"); <\/code><\/pre>\n\n\n\n
    });<\/code><\/pre>\n\n\n\n
}<\/code><\/pre>\n\n\n\n
To configure multiple middleware, use Use()<\/code> extension method. It is similar to Run()<\/code> method except that it includes next parameter to invoke next middleware in the sequence. Consider the following example.<\/p>\n\n\n\n
Example: Use()<\/p>\n\n\n\n
 Copy<\/p>\n\n\n\n
public <\/code>void Configure(<\/code>IApplicationBuilder app, <\/code>IHostingEnvironment env)<\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    app.Use(<\/code>async (context, next) =><\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        <\/code>await context.Response.WriteAsync(<\/code>\"Hello World From 1st Middleware!\");<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
        await next();<\/code><\/pre>\n\n\n\n
    });<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
    app.Run(<\/code>async (context) =><\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        <\/code>await context.Response.WriteAsync(<\/code>\"Hello World From 2nd Middleware\"); <\/code><\/pre>\n\n\n\n
    });<\/code><\/pre>\n\n\n\n
}<\/code><\/pre>\n\n\n\n
The above example will display Hello World From 1st Middleware!Hello World From 2nd Middleware!<\/code> in the browser.<\/p>\n\n\n\n
Thus, we can use Use()<\/code> method to configure multiple middlewares in the order we like.<\/p>\n\n\n\n
Add Built-in Middleware Via NuGet<\/h2>\n\n\n\n
ASP.NET Core is a modular framework. We can add server side features we need in our application by installing different plug-ins via NuGet. There are many middleware plug-ins available which can be used in our application.<\/p>\n\n\n\n
The followings are some built-in middleware:<\/p>\n\n\n\n
Middleware<\/td>Description<\/td><\/tr><\/thead>
Authentication<\/td>Adds authentication support.<\/td><\/tr>
CORS<\/td>Configures Cross-Origin Resource Sharing.<\/td><\/tr>
Routing<\/td>Adds routing capabilities for MVC or web form<\/td><\/tr>
Session<\/td>Adds support for user session.<\/td><\/tr>
StaticFiles<\/td>Adds support for serving static files and directory browsing.<\/td><\/tr>
Diagnostics<\/td>Adds support for reporting and handling exceptions and errors.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Let’s see how to use Diagnostics middleware.<\/p>\n\n\n\n
Diagnostics Middleware<\/h2>\n\n\n\n
Let’s install and use Diagnostics middleware. Diagnostics middleware is used for reporting and handling exceptions and errors in ASP.NET Core, and diagnosing Entity Framework Core migrations errors.<\/p>\n\n\n\n
Open project.json and add Microsoft.AspNetCore.Diagnostics dependency if it is not added. Wait for some time till Visual Studio restores the packages.<\/p>\n\n\n\n
This package includes following middleware and extension methods for it.<\/p>\n\n\n\n
Middleware<\/td>Extension Method<\/td>Description<\/td><\/tr><\/thead>
DeveloperExceptionPageMiddleware<\/td>UseDeveloperExceptionPage()<\/td>Captures synchronous and asynchronous exceptions from the pipeline and generates HTML error responses.<\/td><\/tr>
ExceptionHandlerMiddleware<\/td>UseExceptionHandler()<\/td>Catch exceptions, log them and re-execute in an alternate pipeline.<\/td><\/tr>
StatusCodePagesMiddleware<\/td>UseStatusCodePages()<\/td>Check for responses with status codes between 400 and 599.<\/td><\/tr>
WelcomePageMiddleware<\/td>UseWelcomePage()<\/td>Display Welcome page for the root path.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
We can call respective Use* extension methods to use the above middleware in the configure method of Startup class.<\/p>\n\n\n\n
Let’s add welcomePage middleware which will display welcome page for the root path.<\/p>\n\n\n\n
Example: Add Diagnostics Middleware<\/p>\n\n\n\n
 Copy<\/p>\n\n\n\n
public <\/code>void Configure(<\/code>IApplicationBuilder app, <\/code>IHostingEnvironment env)<\/code><\/pre>\n\n\n\n
{   <\/code><\/pre>\n\n\n\n
    app.UseWelcomePage(); <\/code><\/pre>\n\n\n\n
    <\/code>\/\/other code removed for clarity <\/code><\/pre>\n\n\n\n
}<\/code><\/pre>\n\n\n\n
The above example will display the following welcome page for each request.<\/p>\n\n\n\n\n\n
This way we can use different Use* extension methods to include different middleware.<\/p>\n\n\n\n
Next, learn how to implement logging functionality in the ASP.NET Core application.<\/p>\n\n\n\n
Add Custom Middleware in ASP.NET Core Application<\/h1>\n\n\n\n
Here, you will learn how to create and add your own custom middleware into the request pipeline of ASP.NET Core application.<\/p>\n\n\n\n
The custom middleware component is like any other .NET class with Invoke()<\/code> method. However, in order to execute next middleware in a sequence, it should have RequestDelegate<\/code> type parameter in the constructor.<\/p>\n\n\n\n
Visual Studio includes template for creating standard middleware class. For this, right click on the project or folder where you want to create middleware class and select Add -> New Item. This will open Add New Item popup. Search for word “middleware” in the top right search box as shown below.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/a>Add Custom Middleware<\/p>\n\n\n\n
Select Middleware Class item and give it a name and click on Add button. This will add a new class for the middleware with extension method as shown below.<\/p>\n\n\n\n
Example: Custom Middleware<\/p>\n\n\n\n
 Copy<\/p>\n\n\n\n
\/\/ You may need to install the Microsoft.AspNetCore.Http.Abstractions package into your project<\/code><\/pre>\n\n\n\n
public <\/code>class <\/code>MyMiddleware<\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    <\/code>private <\/code>readonly <\/code>RequestDelegate _next;<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
    <\/code>public MyMiddleware(<\/code>RequestDelegate next)<\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        _next = next;<\/code><\/pre>\n\n\n\n
    }<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
    <\/code>public Task Invoke(<\/code>HttpContext httpContext)<\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
        <\/code>return _next(httpContext);<\/code><\/pre>\n\n\n\n
    }<\/code><\/pre>\n\n\n\n
}<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
\/\/ Extension method used to add the middleware to the HTTP request pipeline.<\/code><\/pre>\n\n\n\n
public <\/code>static <\/code>class <\/code>MyMiddlewareExtensions<\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    <\/code>public <\/code>static <\/code>IApplicationBuilder UseMyMiddleware(<\/code>this <\/code>IApplicationBuilder builder)<\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        <\/code>return builder.UseMiddleware<<\/code>MyMiddleware>();<\/code><\/pre>\n\n\n\n
    }<\/code><\/pre>\n\n\n\n
} <\/code><\/pre>\n\n\n\n
As you can see above, the Invoke() method is not asynchronous. So, change it to asynchronous and write your custom logic before calling next();<\/p>\n\n\n\n
Example: Async Middleware<\/p>\n\n\n\n
 Copy<\/p>\n\n\n\n
public <\/code>class <\/code>MyMiddleware<\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    <\/code>private <\/code>readonly <\/code>RequestDelegate _next;<\/code><\/pre>\n\n\n\n
    <\/code>private <\/code>readonly ILogger _logger;<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
    <\/code>public MyMiddleware(<\/code>RequestDelegate next, <\/code>ILoggerFactory logFactory)<\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        _next = next;<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
        _logger = logFactory.CreateLogger(<\/code>\"MyMiddleware\");<\/code><\/pre>\n\n\n\n
    }<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
    <\/code>public <\/code>async <\/code>Task Invoke(<\/code>HttpContext httpContext)<\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        _logger.LogInformation(<\/code>\"MyMiddleware executing..\");<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
        <\/code>await _next(httpContext); <\/code>\/\/ calling next middleware<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
    }<\/code><\/pre>\n\n\n\n
}<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
\/\/ Extension method used to add the middleware to the HTTP request pipeline.<\/code><\/pre>\n\n\n\n
public <\/code>static <\/code>class <\/code>MyMiddlewareExtensions<\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    <\/code>public <\/code>static <\/code>IApplicationBuilder UseMyMiddleware(<\/code>this <\/code>IApplicationBuilder builder)<\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        <\/code>return builder.UseMiddleware<<\/code>MyMiddleware>();<\/code><\/pre>\n\n\n\n
    }<\/code><\/pre>\n\n\n\n
} <\/code><\/pre>\n\n\n\n
Add Custom Middleware<\/h2>\n\n\n\n
Now, we need to add our custom middleware in the request pipeline by using Use extension method as shown below.<\/p>\n\n\n\n
Example: Add Middleware into Request Pipeline<\/p>\n\n\n\n
 Copy<\/p>\n\n\n\n
public <\/code>void Configure(<\/code>IApplicationBuilder app, <\/code>IHostingEnvironment env)<\/code><\/pre>\n\n\n\n
{<\/code><\/pre>\n\n\n\n
    app.UseMyMiddleware();<\/code><\/pre>\n\n\n\n
 <\/code><\/pre>\n\n\n\n
    app.Run(<\/code>async (context) =><\/code><\/pre>\n\n\n\n
    {<\/code><\/pre>\n\n\n\n
        <\/code>await context.Response.WriteAsync(<\/code>\"Hello World!\");<\/code><\/pre>\n\n\n\n
    });<\/code><\/pre>\n\n\n\n
}<\/code><\/pre>\n\n\n\n
We can add middleware using app.UseMiddleware<MyMiddleware>()<\/code> method of IApplicationBuilder also.<\/p>\n\n\n\n
Thus, we can add custom middleware in the ASP.NET Core application.<\/p>\n\n\n\n
Configure the Default File to be Served on the Root Request<\/p>\n\n\n\n
As we learned in the Set Default File section, app.UseDefaultFiles() middleware serves the following files on the root request.<\/p>\n\n\n\n
    \n
  1. Default.html<\/li>\n\n\n\n
  2. Default.htm<\/li>\n\n\n\n
  3. Index.html<\/li>\n\n\n\n
  4. Index.htm<\/li>\n<\/ol>\n\n\n\n
    Suppose, you want to set home.html as a default page which should be displayed on the root access. To do that, specify DefaultFilesOptions in the UseDefaultFiles method as shown below.<\/p>\n\n\n\n
    public class Startup<\/p>\n\n\n\n
    {<\/p>\n\n\n\n
        public void Configure(IApplicationBuilder app, IHostingEnvironment env)<\/p>\n\n\n\n
        {<\/p>\n\n\n\n
            DefaultFilesOptions options = new DefaultFilesOptions();<\/p>\n\n\n\n
            options.DefaultFileNames.Clear();<\/p>\n\n\n\n
            options.DefaultFileNames.Add(“home.html”);<\/p>\n\n\n\n
            app.UseDefaultFiles(options);<\/p>\n\n\n\n
            app.UseStaticFiles();<\/p>\n\n\n\n
            app.Run(async (context) =><\/p>\n\n\n\n
            {<\/p>\n\n\n\n
                await context.Response.WriteAsync(“Hello World”);<\/p>\n\n\n\n
            });<\/p>\n\n\n\n
        }<\/p>\n\n\n\n
    }<\/p>\n\n\n\n
    Now, this will display home.html from wwwroot folder on the root request http:\/\/localhost:<port><\/em>.<\/p>\n","protected":false},"excerpt":{"rendered":"
    ASP.NET Core – Middleware ASP.NET Core introduced a new concept called Middleware. A middleware is nothing but a component (class) which is executed on every request in ASP.NET Core application. In the classic ASP.NET, HttpHandlers and HttpModules were part of request pipeline. Middleware is similar to HttpHandlers and HttpModules where both needs to be configured and executed […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[13],"tags":[],"class_list":["post-1741","post","type-post","status-publish","format-standard","hentry","category-asp-net-core"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false},"uagb_author_info":{"display_name":"admin","author_link":"http:\/\/waqar-arshad.com\/index.php\/author\/waqar_29_1\/"},"uagb_comment_info":19,"uagb_excerpt":"ASP.NET Core – Middleware ASP.NET Core introduced a new concept called Middleware. A middleware is nothing but a component (class) which is executed on every request in ASP.NET Core application. In the classic ASP.NET, HttpHandlers and HttpModules were part of request pipeline. Middleware is similar to HttpHandlers and HttpModules where both needs to be configured and executed…","_links":{"self":[{"href":"http:\/\/waqar-arshad.com\/index.php\/wp-json\/wp\/v2\/posts\/1741","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/waqar-arshad.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/waqar-arshad.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/waqar-arshad.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/waqar-arshad.com\/index.php\/wp-json\/wp\/v2\/comments?post=1741"}],"version-history":[{"count":2,"href":"http:\/\/waqar-arshad.com\/index.php\/wp-json\/wp\/v2\/posts\/1741\/revisions"}],"predecessor-version":[{"id":2165,"href":"http:\/\/waqar-arshad.com\/index.php\/wp-json\/wp\/v2\/posts\/1741\/revisions\/2165"}],"wp:attachment":[{"href":"http:\/\/waqar-arshad.com\/index.php\/wp-json\/wp\/v2\/media?parent=1741"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/waqar-arshad.com\/index.php\/wp-json\/wp\/v2\/categories?post=1741"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/waqar-arshad.com\/index.php\/wp-json\/wp\/v2\/tags?post=1741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}