We use the set details in the subject when making a request per minute to a given endpoint. We return a header from our server and log it which contains the handling server name. The server handling the request is seldom the same as we would expect with persistent connections.
We reuse the same http_client each request so I would have expected in the general case that the same server would be handling. We use the .NET HttpClient to connect to the same service and see the expected behavior of the same server handling the concurrent requests.
I have also mocked up an example with WinHttp itself doing the same concurrent requests without closing the connection between and it also appears to behave as expected.
We are doing nothing specific around specifying persistent connections, etc. I was wondering if perhaps I have missed something that would allow this behavior to kick in as expected?
Thanks
We reuse the same http_client each request so I would have expected in the general case that the same server would be handling. We use the .NET HttpClient to connect to the same service and see the expected behavior of the same server handling the concurrent requests.
I have also mocked up an example with WinHttp itself doing the same concurrent requests without closing the connection between and it also appears to behave as expected.
We are doing nothing specific around specifying persistent connections, etc. I was wondering if perhaps I have missed something that would allow this behavior to kick in as expected?
Thanks