Currently because the client HttpContext ^1 is shared across executions of different requests there is a concurrency issue as the context should not be considered thread safe.
IMPORTANT: Please note HTTP context implementation, even when thread safe, may not be used concurrently by multiple threads, as the context may contain thread unsafe attributes. ^3
This can cause issues with the authentication state (http.auth.target-scope) used in the request execution phase and user token (http.user-token) used to determine connection reuse from the pool. Both properties are stored in the context.
Currently because the client HttpContext ^1 is shared across executions of different requests there is a concurrency issue as the context should not be considered thread safe.
This can cause issues with the authentication state (
http.auth.target-scope
) used in the request execution phase and user token (http.user-token
) used to determine connection reuse from the pool. Both properties are stored in the context.Relates to ^2.