client sends tcp reset after 302
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.
for full size image https://i.imgur.com/rQfC4tU.jpg
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.
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.