今天來看一下asp.net core的執(zhí)行管道。先看下官方說明：
從上圖可以拋光，asp.net core的執(zhí)行順序是，當(dāng)收到一個請求后，request請求會先經(jīng)過已注冊的中間件，然后會進(jìn)入到mvc的攔截器管道：
進(jìn)入mvc管道后，根據(jù)以上順序執(zhí)行過濾校正。
OK，根據(jù)以上說明下面我們新建一個MVC的演示，將執(zhí)行方式切換為控臺運(yùn)行：
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
// This method gets called by the runtime. Use this method to add services to the container.public void ConfigureServices(IServiceCollection services){ services.AddControllersWithViews(config=> { Console.WriteLine("execute C"); //config.Filters.Add(new AsyncAuthorizationFilter()); config.Filters.Add(new AuthorizationFilter()); config.Filters.Add(new ResourceFilter()); //config.Filters.Add(new AsyncResourceFilter()); config.Filters.Add(new ActionFilter()); //config.Filters.Add(new AsyncActionFilter()); config.Filters.Add(new ResultFilter()); //config.Filters.Add(new AsyncResultFilter()); config.Filters.Add(new ExceptionFilter()); //config.Filters.Add(new AsyncExceptionFilter()); Console.WriteLine("execute D"); }); services.AddSession(config=> { Console.WriteLine("execute E"); });}// This method gets called by the runtime. Use this method to configure the HTTP request pipeline.public void Configure(IApplicationBuilder app, IWebHostEnvironment env){ if (env.IsDevelopment()) { app.UseDeveloperExceptionPage(); } else { app.UseExceptionHandler("/Home/Error"); } app.UseStaticFiles(); app.UseRouting(); app.UseAuthorization(); app.Use(async (context, next) => { Console.WriteLine("execute F"); await context.Response.WriteAsync("hello world"); Console.WriteLine("execute G"); }); //app.UseSession(); app.UseEndpoints(endpoints => { Console.WriteLine("execute A"); endpoints.MapControllerRoute( name: "default", pattern: "{controller=Home}/{action=Index}/{id?}"); Console.WriteLine("execute B"); });} |
執(zhí)行結(jié)果：
不多做解釋，從從這里我們可以拋光符合官方說明文檔。
看完中間件執(zhí)行順序，下面我們來了解下mvc攔截器的使用與執(zhí)行順序。
根據(jù)mvc filter管道執(zhí)行順序，我們分別來看下用法：
1）AuthorizationFilter：該攔截器是優(yōu)先級最高的，當(dāng)請求進(jìn)入mvc后，首先會被AuthorizationFilter驗證是否有權(quán)限訪問，無權(quán)限則跳出。
同步用法：
|
1
2
3
4
5
6
7
|
public class AuthorizationFilter: IAuthorizationFilter{ public void OnAuthorization(AuthorizationFilterContext context) { context.HttpContext.Response.WriteAsync("authorization filter \r"); }} |
異步用法：
|
1
2
3
4
5
6
7
|
public class AsyncAuthorizationFilter: IAsyncAuthorizationFilter{ public async Task OnAuthorizationAsync(AuthorizationFilterContext context) { await context.HttpContext.Response.WriteAsync($"async authorization filter in \r"); }} |
2）ResourceFilter：該攔截器是作為第二道攔截器，
OnResourceExecuting在模型綁定之前運(yùn)行代碼。OnResourceExecuted在管道的其余階段完成之后運(yùn)行代碼。
同步用法：
|
1
2
3
4
5
6
7
8
9
10
11
|
public class ResourceFilter: IResourceFilter{ public void OnResourceExecuting(ResourceExecutingContext context) { context.HttpContext.Response.WriteAsync($"resource executing\r"); } public void OnResourceExecuted(ResourceExecutedContext context) { context.HttpContext.Response.WriteAsync($"resource executed \r"); }} |
異步用法：
|
1
2
3
4
5
6
7
8
9
|
public class AsyncResourceFilter: IAsyncResourceFilter{ public async Task OnResourceExecutionAsync(ResourceExecutingContext context, ResourceExecutionDelegate next) { await context.HttpContext.Response.WriteAsync($" async resource filter in. \r\n"); await next(); await context.HttpContext.Response.WriteAsync($"async resource filter out. \r\n"); }} |
3）ActionFilter：在調(diào)用操作方法之前和之后立即運(yùn)行代碼；可以更改傳遞到操作中的參數(shù)；可以更改從操作返回的結(jié)果。
同步用法：
|
1
2
3
4
5
6
7
8
9
10
11
12
|
public class ActionFilter: IActionFilter{ public void OnActionExecuting(ActionExecutingContext context) { context.HttpContext.Response.WriteAsync($"action executing \r"); } public void OnActionExecuted(ActionExecutedContext context) { context.HttpContext.Response.WriteAsync($"action executed . \r"); }} |
異步用法：
|
1
2
3
4
5
6
|
public async Task OnActionExecutionAsync(ActionExecutingContext context, ActionExecutionDelegate next){ await context.HttpContext.Response.WriteAsync($"async action execution in. \r\n"); await next(); await context.HttpContext.Response.WriteAsync($"async action execution out. \r\n");} |
4）OnException：在向響應(yīng)正文寫入任何內(nèi)容之前，對聲明處理的異常應(yīng)用變量策略。
同步用法：
|
1
2
3
4
5
6
7
|
public class ExceptionFilter: IExceptionFilter{ public void OnException(ExceptionContext context) { context.HttpContext.Response.WriteAsync($"exception \r"); }} |
異步用法：
|
1
2
3
4
5
6
7
8
|
public class AsyncExceptionFilter: IAsyncExceptionFilter{ public Task OnExceptionAsync(ExceptionContext context) { context.HttpContext.Response.WriteAsync($"exception async \r"); return Task.CompletedTask; }} |
5）ResultFilter：在執(zhí)行操作結(jié)果之前和之后立即運(yùn)行代碼；僅當(dāng)操作方法成功執(zhí)行時，其才會運(yùn)行。 可以設(shè)置格式化返回結(jié)果：
同步操作：
|
1
2
3
4
5
6
7
8
9
10
11
|
public class ResultFilter: IResultFilter{ public void OnResultExecuting(ResultExecutingContext context) { context.HttpContext.Response.WriteAsync($"result executing\r"); } public void OnResultExecuted(ResultExecutedContext context) { context.HttpContext.Response.WriteAsync($"result executed \r"); }} |
異步用法：
|
1
2
3
4
5
6
7
8
9
|
public class AsyncResultFilter: IAsyncResultFilter{ public async Task OnResultExecutionAsync(ResultExecutingContext context, ResultExecutionDelegate next) { await context.HttpContext.Response.WriteAsync($"result execution async in \r"); await next(); await context.HttpContext.Response.WriteAsync($"result execution async out. \r"); }} |
注冊方式我們就是用分區(qū)注冊，已經(jīng)在上面說明，不再多做表述，下面我們看下運(yùn)行情況（頁面輸出）：
定義一個異常看下結(jié)果：
|
1
2
3
4
|
public IActionResult Privacy(){ throw new Exception("error");} |
ok，目標(biāo)達(dá)成，不多說了，下次再看攔截器具體實現(xiàn)。
參考文檔：ASP.NET Core 中的篩選器
總結(jié)
到此這篇關(guān)于asp.net mvc core管道及攔截器的文章就介紹到這了,更多相關(guān)asp.net mvc core管道及攔截器內(nèi)容請搜索服務(wù)器之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持服務(wù)器之家！
原文鏈接：https://www.cnblogs.com/xtt321/p/12467142.html
