The following is wireshark trace. In this case, is it a client issue or server issue?
No. Time Source Destination Protocol Length Info 964401 653.881334 192.168.1.8 141.226.106.61 TCP 1494 52696 → 443 [ACK] Seq=7805382 Ack=9895 Win=131840 Len=1440 [TCP segment of a reassembled PDU] 964402 653.881334 192.168.1.8 141.226.106.61 TCP 1494 52696 → 443 [ACK] Seq=7806822 Ack=9895 Win=131840 Len=1440 [TCP segment of a reassembled PDU] 964403 653.881334 192.168.1.8 141.226.106.61 TCP 1494 52696 → 443 [ACK] Seq=7808262 Ack=9895 Win=131840 Len=1440 [TCP segment of a reassembled PDU] 964404 653.881334 192.168.1.8 141.226.106.61 TCP 1494 52696 → 443 [ACK] Seq=7809702 Ack=9895 Win=131840 Len=1440 [TCP segment of a reassembled PDU] 964405 653.881334 192.168.1.8 141.226.106.61 TCP 1494 52696 → 443 [ACK] Seq=7811142 Ack=9895 Win=131840 Len=1440 [TCP segment of a reassembled PDU] 964406 653.881334 192.168.1.8 141.226.106.61 TCP 1494 52696 → 443 [ACK] Seq=7812582 Ack=9895 Win=131840 Len=1440 [TCP segment of a reassembled PDU] 964407 653.881334 192.168.1.8 141.226.106.61 TCP 1494 [TCP Window Full] 52696 → 443 [ACK] Seq=7814022 Ack=9895 Win=131840 Len=1440 [TCP segment of a reassembled PDU] 964414 653.919491 141.226.106.61 192.168.1.8 TCP 60 443 → 52696 [RST] Seq=9895 Win=0 Len=0 964415 653.919491 141.226.106.61 192.168.1.8 TCP 60 443 → 52696 [RST] Seq=9895 Win=0 Len=0 964416 653.919491 141.226.106.61 192.168.1.8 TCP 60 443 → 52696 [RST] Seq=9895 Win=0 Len=0 964417 653.921662 141.226.106.61 192.168.1.8 TCP 60 443 → 52696 [RST] Seq=9895 Win=0 Len=0 964418 653.921662 141.226.106.61 192.168.1.8 TCP 60 443 → 52696 [RST] Seq=9895 Win=0 Len=0 964419 653.921662 141.226.106.61 192.168.1.8 TCP 60 443 → 52696 [RST] Seq=9895 Win=0 Len=0 964420 653.921662 141.226.106.61 192.168.1.8 TCP 60 443 → 52696 [RST] Seq=9895 Win=0 Len=0 964421 653.921662 141.226.106.61 192.168.1.8 TCP 60 443 → 52696 [RST] Seq=9895 Win=0 Len=0 964422 653.921662 141.226.106.61 192.168.1.8 TCP 60 443 → 52696 [RST] Seq=9895 Win=0 Len=0
