HttpClient Dns Changes

[MartinMogh]

I have been using this code to avoid dns issues.

  using var socketHandler = new SocketsHttpHandler
  {
      PooledConnectionIdleTimeout = TimeSpan.FromMinutes(1),
      PooledConnectionLifetime = TimeSpan.FromMinutes(5),
  };

  using var httpClient = new HttpClient(socketHandler);

But i am worried that using PooledConnectionLifetime will cancel download of large files.

Is there anyway of avoiding dns issus without PooledConnectionLifetime?

[huoyaoyuan]

You can ultimately do the DNS yourself like #45144 (comment) . This is somehow overkill though.

[MartinMogh]

I was hoping for a simpler solution

[stephentoub]

But i am worried that using PooledConnectionLifetime will cancel download of large files.

It won't. This setting doesn't affect connections actively being used. It determines whether to get rid of idle connections that are too old.

[MartinMogh]

In the microsoft docs it says: "This property defines maximal connection lifetime in the pool regardless of whether the connection is idle or active."

[stephentoub]

I realize that's confusing wording, but it means it's counting all of the time the connection has been alive, regardless of whether that time was spent idle or active. It will only tear down a connection that's idle.

[stephentoub]

(I opened dotnet/dotnet-api-docs#8241 to clarify.)

[MartinMogh]

thank you