You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 20, 2022. It is now read-only.
There are no guarantees that HttpContext is still gonna be valid when client closes connection.
And at least using it with heavy-loaded Kestrel it seems to be always the case and results logging not working at all.
There are also no guarantees that logging is gonna be used in environment where HttpContext even exists.
And HttpContext here seems to be only used for throwing exceptions and the need of it probably can just be removed.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Log4Net.Async/src/Log4Net.Async/AsyncForwardingAppenderBase.cs
Line 30 in 122bfac
Log4Net.Async/src/Log4Net.Async/ParallelForwardingAppender.cs
Line 200 in 122bfac
There are no guarantees that HttpContext is still gonna be valid when client closes connection.
And at least using it with heavy-loaded Kestrel it seems to be always the case and results logging not working at all.
There are also no guarantees that logging is gonna be used in environment where HttpContext even exists.
And HttpContext here seems to be only used for throwing exceptions and the need of it probably can just be removed.
The text was updated successfully, but these errors were encountered: