You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have currently deployed more than 2 servers to receive QUIC connections. When using lsquic, the sess_resume information of the previous connection establishment will be saved, and this information will be carried when establishing the next connection. Carrying sess_resume on the same server indeed works well. Through the on_hsk_done callback, it can be judged that the enumeration value is LSQ_HSK_RESUMED_OK. However, when I use the sess_resume saved after connecting to server A to connect to server B, the on_hsk_done callback still gives me LSQ_HSK_RESUMED_OK, but actually, by packet capturing, it can be seen that the process of re-handshake has been gone through.
I would like to know if there are any other ways besides on_hsk_done to confirm whether the handshake process has been re-performed when establishing a connection with sess_resume carried? The following is the brief information of the captured data packets.
I have currently deployed more than 2 servers to receive QUIC connections. When using lsquic, the sess_resume information of the previous connection establishment will be saved, and this information will be carried when establishing the next connection. Carrying sess_resume on the same server indeed works well. Through the on_hsk_done callback, it can be judged that the enumeration value is LSQ_HSK_RESUMED_OK. However, when I use the sess_resume saved after connecting to server A to connect to server B, the on_hsk_done callback still gives me LSQ_HSK_RESUMED_OK, but actually, by packet capturing, it can be seen that the process of re-handshake has been gone through.
I would like to know if there are any other ways besides on_hsk_done to confirm whether the handshake process has been re-performed when establishing a connection with sess_resume carried? The following is the brief information of the captured data packets.
First connection to server A:
Second connection to server A with sess_resume carried:
Third connection to server B using the sess_resume returned by server A:
The text was updated successfully, but these errors were encountered: