The synchronous method is not supported by 'Microsoft.AspNetCore.TestHost.ClientHandler'

[code-jar]

In dotnet 6.0, HttpMessageHandler provides the synchronous sending method HttpResponseMessage Send(HttpRequestMessage request, CancellationToken cancellationToken)

Microsoft.AspNetCore.TestHost.ClientHandler inherit HttpMessageHandler Not implemented synchronous sending method Send

Failing Test(s)

Stacktrace

System.NotSupportedException: The synchronous method is not supported by 'Microsoft.AspNetCore.TestHost.ClientHandler'.
 If you're using a custom 'HttpMessageHandler' and wish to use synchronous HTTP methods, you must override its 'Send' virtual method.
   at System.Net.Http.HttpMessageHandler.Send(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.DelegatingHandler.Send(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.DelegatingHandler.Send(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.DelegatingHandler.Send(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpMessageInvoker.Send(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.Send(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.Send(HttpRequestMessage request)

[adityamandaleeka]

@code-jar Can you share more about your use case? Is there a reason why you can't use the async version of the API?

Triage: We could implement this pretty trivially with something like SendAsync.GetAwaiter().GetResult().

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[Tratcher]

Implementing this risks causing threadpool exhaustion in the test project. We'll add an error message to that effect.