Hi, Does anyone have an idea what could cause the delay of one second in the below screenshot? It doesn't happen for all requests to the server, but it does so frequently enough. The client uses HTTP 1.0 & doesn't send a keep-alive header, so it is correct the server initiates the closing of the connection. But why does it wait for 1 second before doing that? The server is an IBM HTTP server. Since it isn't 100% doing that, I doubt it's a setting, but I was wondering if there's a way to avoid it or at least understand why it's happening. Thanks
asked 07 Apr '16, 01:01  Sebbe |
One Answer:
Well, the capture file won't tell you. So, one option would be to enable debug logging on the server to figure out whats going on. My best guess would be: It's busy for whatever reason and thus it does not send the FIN earlier. Regards answered 19 Apr '16, 13:58  Kurt Knochner ♦ |
