There may be an intermediary, or several, who is interrupting the request.Your client is on an rfc 1918 address range, so there is some nat going on, probably at your gateway router -- if that is overloaded or malfunctioning, that could cause an issue. Similarly, there is likely to be one or more layers of transparent caching and proxying between you and the origin server, any of those can interpose themselves on the tcp flow.
Does the target server offer https ? Does the problem occur when using https ?
On Thu, Oct 29, 2015 at 10:07 AM, Juli an <julian...@googlemail.com> wrote:
> I am struggling with a very annoying problem. My application does a lot of
> http GET requests to some .NET Application on an IIS 7.5.
> For a random number of requests, the connections return, a status code is
> delivered, body read, everything's fine. But at some point, it does not
> depend on the URL as it seems, the Server sends a lot of packets of the
> 114719 3898.085719000 62.x.x.x 192.168.0.14 TCP 60 80→50748 [RST, ACK]
> Seq=413 Ack=391 Win=0 Len=0
Looks like the server is closing the connection.
> I did try to set timeouts to catch this. The default one and also via custom
> transports like described here:
> Yes I close the response body, this is no issue. (The socket count in the
> running process is low)
> None of them were successful. Do you have an idea how to work around this or
> get it fixed?
Perhaps the server has some kind of rate limiting that prevents the
client from re-establishing a connection.