-
Notifications
You must be signed in to change notification settings - Fork 5.3k
LoggingHttpMessageHandler should log unescaped URL in log message (#62894) #63012
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LoggingHttpMessageHandler should log unescaped URL in log message (#62894) #63012
Conversation
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsModifies the logging in Fix #62894
|
src/libraries/Microsoft.Extensions.Http/src/Logging/LoggingHttpMessageHandler.cs
Outdated
Show resolved
Hide resolved
9f6dde0 to
03e8341
Compare
src/libraries/Microsoft.Extensions.Http/src/Logging/LoggingScopeHttpMessageHandler.cs
Outdated
Show resolved
Hide resolved
src/libraries/Microsoft.Extensions.Http/src/Logging/LoggingHttpMessageHandler.cs
Outdated
Show resolved
Hide resolved
03e8341 to
2fa1722
Compare
…tnet#62894) Modifies the logging in LoggingHttpMessageHandler and LoggingScopeHttpMessageHandler to log the AbsoluteUri so the unescaped Uri is logged
2fa1722 to
212e048
Compare
MihaZupan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
CarnaViire
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Modifies the logging in
LoggingHttpMessageHandlerandLoggingScopeHttpMessageHandlerto log theAbsoluteUriso the unescaped Uri is logged.Fix #62894