Blazor WASM: HttpClient.SendAsync does not set the RequestMessage in ResponseMessage

[ealsur]

Describe the bug

When SendAsync is called on HttpClient, the HttpResponseMessage.RequestMessage is null when the HttpClient is in Blazor WASM, but not null (and equal to the original HttpRequestMessage) on NET Core.

In NET Core, we do:

HttpClient httpclient = new HttpClient();
HttpRequestMessage requestMessage = new HttpRequestMessage(HttpMethod.Get, "https://www.bing.com");
HttpResponseMessage responseMessage = await httpclient.SendAsync(
    requestMessage,
    HttpCompletionOption.ResponseHeadersRead);

In Blazor WASM, we have the HttpClient registered as:

builder.Services.AddScoped(sp => new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) });

And in a Blazor page:

@inject HttpClient Http

HttpRequestMessage requestMessage = new HttpRequestMessage(HttpMethod.Get, "https://localhost:44384/");
HttpResponseMessage responseMessage = await Http.SendAsync(
    requestMessage,
    HttpCompletionOption.ResponseHeadersRead);

To Reproduce

Sample code in this repo: https://github.com/ealsur/httpclientwasm

Running the Console app, the output is:

https://github.com/ealsur/httpclientwasm/blob/master/ConsoleApp/Program.cs#L19

Running the Blazor WASM app and browsing to Fetch Data, shows the output in the Browser Console:

https://github.com/ealsur/httpclientwasm/blob/master/Blazor/Pages/FetchData.razor#L48

[ghost]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[pranavkm]

FYI @kjpou1

[karelz]

Fixed in 6.0/master (PR #42822) and in 5.0 (PR #42849).