`WebApplicationFactory.CreateClient()` with HTTP/2 and/or HTTP/3 option?

[khteh]

https://learn.microsoft.com/en-us/aspnet/core/test/integration-tests?view=aspnetcore-9.0 doesn't show how possible it is to CreateClient with HTTP/2 and/or HTTP/3 protocol. WebApplicationFactoryClientOptions doesn't seem to have this config. Please advise!

[martincostello]

Use HttpClient.DefaultRequestVersion on the client to change the HTTP version.

However, be aware that the HttpClient used with WebApplicationFactory uses an in-memory transport, so no actual network communication happens so I don't think it'll make any difference if you change it.

[khteh]

Then how would any other option matter at all?

        BaseAddress = clientOptions.BaseAddress;
        AllowAutoRedirect = clientOptions.AllowAutoRedirect;
        MaxAutomaticRedirections = clientOptions.MaxAutomaticRedirections;
        HandleCookies = clientOptions.HandleCookies;

[martincostello]

The in-memory implementation deals with a variety of them under the hood. Of the four you've mentioned, all four are understood and useful, even if they're not talking to a real server over the network.

[khteh]

How about the scheme - HTTP vs HTTPS, and the port numbers? Do they make any difference?

[martincostello]

Lots of things still make a difference. Just try them out, or look into the source code for the Mvc.Testing package.

[khteh]

Use HttpClient.DefaultRequestVersion on the client to change the HTTP version.

However, be aware that the HttpClient used with WebApplicationFactory uses an in-memory transport, so no actual network communication happens so I don't think it'll make any difference if you change it.

'WebApplicationFactoryClientOptions' does not contain a definition for 'DefaultRequestVersion'

[martincostello]

Change it on the HttpClient, where the option I pointed you to is. It even says HttpClient in the text of the quoted reply.