ssl handshake diagram

3626544837IP 192.168.1.116.3337 > 192.168.1.123.7788:ack 1739326487,ack 1First handshake: 192.168.1.116 sends a bit code syn=1, randomly generates a SEQ number=3626544836 packet to 192.168.1.123,192.168.1.123 by syn= 1 know 192.168.1.116 requirements to establish online;Second handshake: 192.168.1.123 to confirm the online information after receiving the request, send Ack number=3626544837,syn=1,ack=1 to 1

messages to each other, that is, close the connection. So what you need to accomplish in the close_wait state is waiting for you to close the connection .Last_ack: This state is still relatively easy to understand, it is the passive close side after sending fin messages, and finally wait for each other's ACK message. When an ACK message is received, it is also possible to enter the closed available state.Thinking:To be Continued ...Reference:Time_wait status in TCP connections-Sunnydogzhou's co

to the server. But the server thought the new transport connection had been established and waited for the client to send the data. In this way, many of the server's resources are wasted. The use of "three-time handshake" method can prevent the above phenomenon. For example, in that case, the client does not issue confirmation to the server's confirmation. The server knows that the client does not require a connection because it cannot receive a conf

Let's talk about the TCP three handshake and the TCP state transition diagram today. First, a three-time handshake flow chart is as follows: 2.4-3, three-way AC-Grip Packet Connection mode A: Packet Initiation When the client wants to initiate a connection to the server, it is necessary to send a packet that requires a con

to turn off the client to server data transfer, the client enters the fin_wait_1 state.(2) Second wave: After receiving fin, the server sends an ACK to the client, confirming that the sequence number is received sequence number +1 (same as SYN, one fin occupies a serial number), and the server enters the close_wait state.(3) Third wave: The server sends a fin to shut down the server-to-client data transfer, and the server enters the Last_ack state.(4) The fourth wave: After the client receives

sending, resulting in one more. What if a connection has been established, but the client suddenly fails? TCP also has a keepalive timer, obviously, if the client fails, the server can not continue to wait, wasted resources. The server resets the timer after each client request, usually set to 2 hours, and if two hours has not received any data from the client, the server sends a probe segment, which is sent every 75 minutes thereafter. If a 10 probe packet is still not

response is obtained through the Content-type field: content-type:image/png; or the content-type:text/html we're familiar with.The following are the values of some common content-type fields.Text/plainText/htmlText/cssImage/jpegImage/pngImage/svg+xmlAudio/mp4Video/mp4Application/javascriptApplication/pdfApplication/zipApplication/atom+xml5. The browser parses the HTML code and requests the resources in the HTML codeSometimes we get an HTML page, in the process of parsing the browser to HTML, if

The idea of the APR connector and the overall architecture of the Bio,nio are similar, you can see the following overall block diagram: The first difference is that for the socket from the acceptor thread parsing this piece, whether it is nio or bio are inAcceptorthread within the direct blocking execution, for the APR channel, make a socketwithoptions thread, specifically to perform this socket parsing work, and then directly to the Poller thread for