client sends tcp reset after 302

asked 2018-11-29 16:24:41 +0000

pr0n gravatar image

updated 2018-11-29 16:28:29 +0000

As shown in the screenshot below when a client receives a 302 as expected it then sends a TCP RST. Why is this? Is this correct, I have searched HTTP1.0 and 1.1 RFCs and do not see an explanation for this behavior.

image descriptionfor full size image

edit retag flag offensive close merge delete


To be pedantic the client sends the RST after the server responds with a SYN + ACK to the client SYN, i.e. the client started a new connection (2 off) and then closed them straight away.

grahamb gravatar imagegrahamb ( 2018-11-29 17:27:14 +0000 )edit

Right, I see this on all clients. Even purpose built load test clients, so I assume it must be written in a spec somewhere but at a glance it appears totally superfluous.

pr0n gravatar imagepr0n ( 2018-11-29 18:23:56 +0000 )edit