Timeline for What is "TIME_WAIT" connection in a TCP connection and what is it's purpose?
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 4, 2021 at 19:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 16, 2020 at 23:41 | comment | added | Ron Maupin♦ | Did any answer help you? If so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you can post and accept your own answer. | |
| Dec 6, 2020 at 3:06 | comment | added | samshers | @ricky, port 53948 is my concern. What's is it's purpose. | |
| Dec 5, 2020 at 21:49 | comment | added | Ricky | Connections are constantly being created/closed/destroyed. You're just catching them in those various states. (web traffic isn't normally a long lived, persistent socket.) As this is a localhost socket, you're seeing both ends. | |
| Dec 5, 2020 at 18:04 | review | Close votes | |||
| Dec 5, 2020 at 20:22 | |||||
| Dec 5, 2020 at 17:45 | comment | added | samshers | I don't think this addresses the additional port issue which is also my concern @ricky | |
| Dec 5, 2020 at 17:39 | comment | added | Ricky | Does this answer your question? What is the purpose of TIME WAIT in TCP connection tear down? (literally the first google result, superuser answer from 2010 is 2nd) | |
| Dec 5, 2020 at 17:38 | comment | added | Ricky | Granted, it might take someone a while to zero in on RFC 793, but it took me a faction of a second to search for TIME WAIT ("TIME-WAIT") to highlight the text in my answer. (I'd vote to close this if "lack of research" were still a close reason) | |
| Dec 5, 2020 at 17:36 | comment | added | samshers | @ricky, agree with u. It just takes bit of time and patience + intel | |
| Dec 5, 2020 at 17:34 | comment | added | Ricky | Yes, RFC's may look like an alien language, but they are perfectly clear english. I know reading is hard, and it's a long block of monospaced text, but it is very clearly documented. | |
| Dec 5, 2020 at 17:31 | answer | added | Ricky | timeline score: 1 | |
| Dec 5, 2020 at 17:22 | comment | added | Zac67♦ |
A new socket connection uses a new ephemeral port - possibly, there's a redirect. Try your browser's network/diagnostic tools, wget, curl, or similar. Also, what you're really asking about is the workings of HTTP which are off-topic here as an application-layer protocol...
|
|
| Dec 5, 2020 at 16:44 | comment | added | Ron Maupin♦ | There is a clear diagram on page 23 that explains the different states and how to get to them. | |
| Dec 5, 2020 at 14:48 | comment | added | samshers | @zac67, thx. How about the additional ports - would the RFC capture this too. I will appreciate if u can summarize in to an answer. RFC's are generally not English :-) for every one. | |
| Dec 5, 2020 at 14:44 | comment | added | Zac67♦ | Have you tried RFC 793? | |
| Dec 5, 2020 at 12:57 | history | asked | samshers | CC BY-SA 4.0 |