Usage WinHttpHandler vs HttpClientHandler for apps written on Net Framework

Question

There are at least 2 handlers which we can use in HttpClient for apps written by Net Framework 4.6.1+, i.e.:

HttpClientHandler (part of Net Framework)
WinHttpHandler (supplied via Nuget)

There are no articles comparing them by next questions:

performance comparison
working with DNS shift (when IPs for DNS FQDN is changed)
connection lease timeout (when HttpClient doesn't automatically move to new instance when autoscaling)

Could anyone share your experience of usage WinHttpHandler?

Community · Accepted Answer · 2020-06-20 09:12:55Z

5

Karel Zikmund wrote answer on my question, you can see it via next url

Starting with .NET Core 2.1, the HttpClientHandler uses by default SocketsHttpHandler - new C# implementation over sockets.

It's key value is consistency across platforms and focus on performance (especially against CurlHandler on Linux/Mac).

WinHttpHandler is wrapper over winhttp OS component. If you need HTTP/2, it is currently the only option as SocketsHttpHandler does not support HTTP/2 yet (see #23134).

DNS changes behave the same behavior on both, however, you can tweak it somewhat via SocketsHttpHandler.PooledConnectionLifetime.

DNS TTL is not supported - see #24257 and #11224. The workaround is to recycle the handler on regular basis. You can also use higher-level wrapper HttpClientFactory which does that for you (at least as a motivation).

edited Jun 20, 2020 at 9:12

CommunityBot

11 silver badge

answered Jul 22, 2018 at 19:27

StuS

85711 silver badges14 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Usage WinHttpHandler vs HttpClientHandler for apps written on Net Framework

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related