client sends tcp reset after 302

  • retag add tags

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 https://i.imgur.com/rQfC4tU.jpg

pr0n's avatar
3
pr0n
asked 2018-11-29 16:24:41 +0000, updated 2018-11-29 16:28:29 +0000
edit flag offensive 0 remove flag close merge delete

Comments

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's avatar grahamb (2018-11-29 17:27:14 +0000) edit
more
  • delete

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's avatar pr0n (2018-11-29 18:23:56 +0000) edit
more
  • delete
add a comment see more comments