HttpContext lost between HttpClientWrapper and DelegatingHandler

Expected Behavior / New Feature

A DelegatingHandler with IHttpContextAccessor injected can access the current context correctly.

Actual Behavior / Motivation for New Feature

As of version 15.0.7, a custom DelegatingHandler we use now only has access to an empty context and thus httpContextAccessor.HttpContext.User.FindFirst(ClaimTypes.NameIdentifier)?.Value is now null instead of the name like it was in 15.0.6

Steps to Reproduce the Problem

1. Create a DelegatingHandler that takes in IHttpContextAccessor as an injected dependency.
2. Register the handler on the route.
3. Add JWT auth to the route.
4. In the SendAsync method, call httpContextAccessor.HttpContext.User.FindFirst(ClaimTypes.NameIdentifier)?.Value
5. See that the value is null

Specifications

• Version: 15.0.7
• Platform: dotnet 3.1.300
• Subsystem: MacOS

[AgentShark]

@raman-m I use v18.0.0 where the issue is still present.

[amweiss]

I no longer use this project so I won’t be going back to verify.