ModernHttpClient support?

[omares]

Hey, is there a way to use the ModernHttpClient instead of HttpClient?

[tmenier]

Sure. Looks like ModernHttpClient is implemented via a custom HttpMessageHandler, which is simple to wire into all Flurl.Http calls via a custom factory like this:

using Flurl.Http.Configuration;

public class ModernHttpClientFactory : DefaultHttpClientFactory
{
    public override HttpMessageHandler CreateMessageHandler() {
        return new ModernHttpClient.NativeMessageHandler();
    }
}

Then on app startup, register it with Flurl thusly:

FlurlHttp.Configure(c => {
    c.HttpClientFactory = new ModernHttpClientFactory();
});

Let me know if this works for you.

[tmenier]

Closing this issue. If for some reason it did not work, feel free to re-open or just comment.

[NateRickard]

Just confirming - this does seem to work and is exactly what I was looking for. I suggest you add this example to your docs under /extensibility.

[tmenier]

Great. Yeah I was just reminded in another issue that CreateMessageHandler needs to be documented.

Nice to see Flurl getting some traction with Xamarin users, would love to figure out how to get the word out more broadly.

[galmok]

What if we do not want to make a global Flurl configuration, but decide on a per request which httpclient is to be used?

In our case we want to selectively ignore certificate validation.

[tmenier]

@galmok No problem - the same global settings object is available per FlurlClient instance via the Settings property.

var client = new FlurlClient();
client.Settings.HttpClientFactory = new MyCustomFactory();
var result = await "http://api.com".WithClient(client).GetAsync();

The docs need to be updated in this area.