You can take advantage of HttpClientFactory to preconfigure named HttpClient instances. Note that the HttpClientFactory is a central location that can be used to register, configure, and consume ...
If you took a dependency on Netstandard2.0 (drop support for .NET Framework <= 4.7.1 I think), you could use the official HttpClientFactory, allowing your library/end-users to handle DNS changes ...
Though this class implements IDisposable, declaring and instantiating it within a using statement is not preferred because when the HttpClient object gets disposed of, the underlying socket is not ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results