Investigate setting a non-infinite `PooledConnectionLifetime` by default
nblumhardt opened this issue ยท 2 comments
nblumhardt commented
Pooled HttpClient
connections (somewhat infamously :-)) have trouble responding to DNS changes; we think we might have observed one recently in datalust/seq-tickets#1651.
On platforms that support SocketsHttpHandler
, we should strongly consider setting a non-infinite PooledConnectionLifetime
if no handler is supplied by the user.
nblumhardt commented
@Mike-E-angelo this change is now published in v5.1.2-dev-00229; we'll be making a 5.2 release within a month or so and rolling this in - any feedback appreciated :-)
Mike-E-angelo commented
Thank you very much @nblumhardt and team for your efforts. ๐
No feedback here as of yet, as long as it works and keeps me off your forums that's all I really care about :D