This repository was archived by the owner on Dec 19, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 308
HostingEngine.Start shouldn't get request ID unless it begins a scope #392
Comments
Had a go at this previously ed1fd4a but it made some tests upset; would need to move some of the code out and into the feature, with the lazy eval |
Yeah we have a changed planned in Logging to make the entire |
Pushing the FastRequestIdentifierFeature up the chain into the HttpContext gets you some of the way there: benaadams/HttpAbstractions@e2ae5ac |
benaadams
added a commit
to benaadams/Hosting
that referenced
this issue
Oct 10, 2015
Resolves aspnet#392 Requires aspnet/HttpAbstractions#420
Should be resolved by #394 but needs the upstream commit; may need test fixes. |
Closed
benaadams
added a commit
to benaadams/Hosting
that referenced
this issue
Oct 12, 2015
Resolves aspnet#392 Requires aspnet/HttpAbstractions#435 Move HttpRequestIdentifierFeature to HttpAbsractions
benaadams
added a commit
to benaadams/Hosting
that referenced
this issue
Oct 12, 2015
Resolves aspnet#392 Requires aspnet/HttpAbstractions#435 Move HttpRequestIdentifierFeature to HttpAbsractions
Just talked to @lodejard. Moving is issues to RC2. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Generating request ID is expensive so
HostingEngine.Start
shouldn't be grabbing the request ID from the feature collection unless it's actually going to callBeginScope
.Effectively we need to merge line 99 into line 110.
by @DamianEdwards
The text was updated successfully, but these errors were encountered: