Hello,
On Mon, 19 Feb 2024 16:24:48 +0800
Kin Seng <ckinseng@gmail.com> wrote:
[...]
> Please refer to the attachments for reference.
>
> On Mon, Feb 19, 2024 at 4:24 PM Kin Seng <ckinseng@gmail.com> wrote:
> > After capturing the tcp packet and check via wireshark, I found out that
> > the nginx is sending out the RST to the public server and then send FIN/ACK
> > (refer attached pcap picture) to client application.
> >
> > I have tried to enable keepalive related parameters as per the nginx
> > config above and also check on the OS's TCP tunable and i could not find
> > any related settings which make NGINX to kill the TCP connection.
> >
> > Anyone encountering the same issues?
> >
The screenshot shows only 1 segment with FIN flag set too which is
odd - there should be one from each party in close sequence. Also the
client only returns an ACK, rather than FIN+ACK, which it should if
nginx was the initiator of closing the connection...
_______________________________________________
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx
