How to evict a TCP connection in pool ?

Jun 2, 2014 at 2:36 PM
As connections are pooled under Windows, I wonder also if it is possible to evict (close) a TCP connection.
As services are usually implemented by servers farms, it may happen that one server is not really up (cannot contact its back-end for example, but still online...). Such a server may answer 'Bad gateway', and in this case the client should retry its request to a physically different server. As unauthenticated connections are pooled under Windows, how can this be achieved with current API ?
Jun 6, 2014 at 6:10 PM
Hi momaison,

We don't currently have an option for doing this. I understand what your saying, but have you actually seen this happen in practice? If the server closes the connection when responding then there might not be an issue.

I took at look at all the options provided by WinHttp (what we build on for Windows desktop) and I don't see any option or ability to configure this, so I'm not sure if it will be possible.