Previously StayRTR would copy the client's Session ID back into the Cache Response to the client, even though the server's internal Session ID was something different.
The purpose of the Session ID is to help both client and server understand whether they are synchronized or not. There are two opportunities to fix desyncs: if the server recognises the client is desynced, the server informs the client (through an Error Report) to reconnect and and send a Reset Query. If the client recognises it is out of sync with the server, the client can send a Reset Query.
Previously StayRTR would copy the client's Session ID back into the Cache Response to the client, even though the server's internal Session ID was something different.
The purpose of the Session ID is to help both client and server understand whether they are synchronized or not. There are two opportunities to fix desyncs: if the server recognises the client is desynced, the server informs the client (through an Error Report) to reconnect and and send a Reset Query. If the client recognises it is out of sync with the server, the client can send a Reset Query.
Related #82