網(wǎng)站首頁(yè) 編程語(yǔ)言 正文
Intro
.NET 6 會(huì)引入一個(gè) Http logging 的中間件,可以用來(lái)幫助我們比較方便記錄請(qǐng)求和響應(yīng)的信息
Sample
廢話不多說(shuō),直接來(lái)看示例吧
var?builder?=?WebApplication.CreateBuilder(args); builder.Services.AddControllers(); var?app?=?builder.Build(); app.UseHttpLogging(); app.MapControllers(); app.Run();
dotnet run
運(yùn)行起來(lái)項(xiàng)目,然后訪問(wèn)一個(gè)接口就可以看到打印出來(lái)的 Http logging 的日志了
info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[1] ??????Request: ??????Protocol:?HTTP/1.1 ??????Method:?GET ??????Scheme:?http ??????PathBase: ??????Path:?/weatherforecast ??????Accept:?text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9 ??????Connection:?keep-alive ??????Host:?localhost:5084 ??????User-Agent:?Mozilla/5.0?(Windows?NT?10.0;?Win64;?x64)?AppleWebKit/537.36?(KHTML,?like?Gecko)?Chrome/94.0.4606.54?Safari/537.36 ??????Accept-Encoding:?gzip,?deflate,?br ??????Accept-Language:?zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7 ??????Cache-Control:?[Redacted] ??????Upgrade-Insecure-Requests:?[Redacted] ??????sec-ch-ua:?[Redacted] ??????sec-ch-ua-mobile:?[Redacted] ??????sec-ch-ua-platform:?[Redacted] ??????Sec-Fetch-Site:?[Redacted] ??????Sec-Fetch-Mode:?[Redacted] ??????Sec-Fetch-User:?[Redacted] ??????Sec-Fetch-Dest:?[Redacted] info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[2] ??????Response: ??????StatusCode:?200 ??????Content-Type:?application/json;?charset=utf-8 ??????Date:?[Redacted] ??????Server:?[Redacted] ??????Transfer-Encoding:?chunked
默認(rèn)地,HttpLoggingMiddleware
會(huì)記錄請(qǐng)求的基本信息(請(qǐng)求地址,協(xié)議版本)和請(qǐng)求頭信息以及響應(yīng)狀態(tài)和響應(yīng)頭信息,對(duì)于不在默認(rèn)列表里的請(qǐng)求頭和響應(yīng)頭,值會(huì)顯示為 [Redacted]
,如果需要記錄這個(gè)請(qǐng)求頭/響應(yīng)頭的值則需要配置 HttpLoggingOptions
,可以在注冊(cè)服務(wù)的時(shí)候進(jìn)行配置,配置示例如下:
builder.Services.AddHttpLogging(options?=> { ????options.RequestHeaders.Add("Cache-Control"); ????options.ResponseHeaders.Add("Server"); });
修改之后,重新啟動(dòng)并請(qǐng)求我們的服務(wù),日志輸出如下:
info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[1] ??????Request: ??????Protocol:?HTTP/1.1 ??????Method:?GET ??????Scheme:?http ??????PathBase: ??????Path:?/weatherforecast ??????Accept:?text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9 ??????Connection:?keep-alive ??????Host:?localhost:5084 ??????User-Agent:?Mozilla/5.0?(Windows?NT?10.0;?Win64;?x64)?AppleWebKit/537.36?(KHTML,?like?Gecko)?Chrome/94.0.4606.54?Safari/537.36 ??????Accept-Encoding:?gzip,?deflate,?br ??????Accept-Language:?zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7 ??????Cache-Control:?max-age=0 ??????Upgrade-Insecure-Requests:?[Redacted] ??????sec-ch-ua:?[Redacted] ??????sec-ch-ua-mobile:?[Redacted] ??????sec-ch-ua-platform:?[Redacted] ??????Sec-Fetch-Site:?[Redacted] ??????Sec-Fetch-Mode:?[Redacted] ??????Sec-Fetch-User:?[Redacted] ??????Sec-Fetch-Dest:?[Redacted] info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[2] ??????Response: ??????StatusCode:?200 ??????Content-Type:?application/json;?charset=utf-8 ??????Date:?[Redacted] ??????Server:?Kestrel ??????Transfer-Encoding:?chunked
注意看一下請(qǐng)求頭里的 Cache-Control
和響應(yīng)頭里的 Server
,原來(lái)都是 [Redacted]
,配置之后就顯示正確的值了,如果你要記錄自定義的請(qǐng)求頭信息,也是類似的配置
接著我們來(lái)配置一下記錄請(qǐng)求信息和響應(yīng)信息,可以配置 HttpLoggingOptions
中的 LoggingFields
來(lái)指定需要記錄哪些信息
builder.Services.AddHttpLogging(options?=> { ????options.LoggingFields?=?Microsoft.AspNetCore.HttpLogging.HttpLoggingFields.All; ????options.RequestHeaders.Add("Cache-Control"); ????options.ResponseHeaders.Add("Server"); });
在上面的基礎(chǔ)上增加 LoggingFields
的配置,這里直接配置上所有的信息,此時(shí)再來(lái)重新請(qǐng)求,查看日志如下:
info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[1] ??????Request: ??????Protocol:?HTTP/1.1 ??????Method:?GET ??????Scheme:?http ??????PathBase: ??????Path:?/weatherforecast ??????Host:?localhost:5084 ??????User-Agent:?dotnet-HTTPie/0.1.1 info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[2] ??????Response: ??????StatusCode:?200 ??????Content-Type:?application/json;?charset=utf-8 info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[4] ??????ResponseBody:?[{"date":"2021-09-25T23:40:11.0164783+08:00","temperatureC":37,"temperatureF":98,"summary":"Cool"},{"date":"2021-09-26T23:40:11.0164836+08:00","temperatureC":50,"temperatureF":121,"summary":"Warm"},{"date":"2021-09-27T23:40:11.0164838+08:00","temperatureC":-7,"temperatureF":20,"summary":"Scorching"},{"date":"2021-09-28T23:40:11.016484+08:00","temperatureC":39,"temperatureF":102,"summary":"Freezing"},{"date":"2021-09-29T23:40:11.0164842+08:00","temperatureC":4,"temperatureF":39,"summary":"Balmy"}]
可以看到此時(shí)的 response body 也記錄下來(lái)了
我們?cè)賮?lái)增加一個(gè) POST 的 API 來(lái)驗(yàn)證一下 RequestBody 是不是可以正常記錄
[HttpPost] public?IActionResult?Post(System.Text.Json.JsonElement?element)?=>?Ok(element);
使用 dotnet-httpie 執(zhí)行 http :5084/weatherforecast name=test
請(qǐng)求一下 API,輸出日志如下:
info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[1] ??????Request: ??????Protocol:?HTTP/1.1 ??????Method:?POST ??????Scheme:?http ??????PathBase: ??????Path:?/weatherforecast ??????Host:?localhost:5084 ??????User-Agent:?dotnet-HTTPie/0.1.1 ??????Content-Type:?application/json;?charset=utf-8 ??????Content-Length:?15 info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[3] ??????RequestBody:?{"name":"test"} info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[2] ??????Response: ??????StatusCode:?200 ??????Content-Type:?application/json;?charset=utf-8 info:?Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware[4] ??????ResponseBody:?{"name":"test"}
More
仔細(xì)看上面的示例的話會(huì)發(fā)現(xiàn)一個(gè)問(wèn)題,當(dāng)要記錄 ResponseBody 的時(shí)候,Response header 的信息沒有被完全記錄下來(lái),感覺像是一個(gè) BUG,提了一個(gè) issue 還沒回復(fù),感興趣的可以參考:<https://github.com/dotnet/aspnetcore/issues/36920>
另外感覺這個(gè)中間件的日志級(jí)別都是 Information 級(jí)別的,如果可以根據(jù)響應(yīng)狀態(tài)來(lái)動(dòng)態(tài)配置日志級(jí)別就好了,比如說(shuō)響應(yīng)狀態(tài)碼大于等于 500 的時(shí)候,日志級(jí)別記錄為 ERROR
, 這樣就可以有效地去除很多不必要的日志了,提了一個(gè)簡(jiǎn)陋的 PR,有興趣的可以參考:https://github.com/dotnet/aspnetcore/pull/36873
原文鏈接:https://jishuin.proginn.com/p/763bfbd6811e
相關(guān)推薦
- 2022-11-14 UNIX環(huán)境高級(jí)編程筆記
- 2022-04-24 基于Python制作一個(gè)文件去重小工具_(dá)python
- 2023-01-26 Redis實(shí)戰(zhàn)之Jedis使用技巧詳解_Redis
- 2022-10-20 Swift協(xié)議Protocol介紹_Swift
- 2022-04-11 socket連接關(guān)閉問(wèn)題分析_python
- 2022-08-01 Qt實(shí)現(xiàn)矩形大小任意縮放的示例代碼_C 語(yǔ)言
- 2022-06-22 git版本庫(kù)介紹及本地創(chuàng)建的三種場(chǎng)景方式_其它綜合
- 2022-11-04 ASP.NET?MVC使用正則表達(dá)式驗(yàn)證手機(jī)號(hào)碼_實(shí)用技巧
- 最近更新
-
- window11 系統(tǒng)安裝 yarn
- 超詳細(xì)win安裝深度學(xué)習(xí)環(huán)境2025年最新版(
- Linux 中運(yùn)行的top命令 怎么退出?
- MySQL 中decimal 的用法? 存儲(chǔ)小
- get 、set 、toString 方法的使
- @Resource和 @Autowired注解
- Java基礎(chǔ)操作-- 運(yùn)算符,流程控制 Flo
- 1. Int 和Integer 的區(qū)別,Jav
- spring @retryable不生效的一種
- Spring Security之認(rèn)證信息的處理
- Spring Security之認(rèn)證過(guò)濾器
- Spring Security概述快速入門
- Spring Security之配置體系
- 【SpringBoot】SpringCache
- Spring Security之基于方法配置權(quán)
- redisson分布式鎖中waittime的設(shè)
- maven:解決release錯(cuò)誤:Artif
- restTemplate使用總結(jié)
- Spring Security之安全異常處理
- MybatisPlus優(yōu)雅實(shí)現(xiàn)加密?
- Spring ioc容器與Bean的生命周期。
- 【探索SpringCloud】服務(wù)發(fā)現(xiàn)-Nac
- Spring Security之基于HttpR
- Redis 底層數(shù)據(jù)結(jié)構(gòu)-簡(jiǎn)單動(dòng)態(tài)字符串(SD
- arthas操作spring被代理目標(biāo)對(duì)象命令
- Spring中的單例模式應(yīng)用詳解
- 聊聊消息隊(duì)列,發(fā)送消息的4種方式
- bootspring第三方資源配置管理
- GIT同步修改后的遠(yuǎn)程分支