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 Nov 20, 2018. It is now read-only.
It's not very common to care about the underlying connection id when logging. It's especially less relevant with http2 since it's the same connection for all requests. Why does it need to be first class?
It's not very common to care about the underlying connection id when logging.
I use it all the time when working with WebSockets. Wasn't that (logging) the reason for it to be added in the first place? (#542)
Why does it need to be first class?
It doesn't need to be first class, but it would be convenient. HttpContext.Features.Get<IHttpConnectionFeature>().ConnectionId is pretty verbose (yes, I have an extension method for it, but still) 😢
What it says on the tin. Is there a reason this isn't exposed through the
HttpContext
surface?The text was updated successfully, but these errors were encountered: