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
This seems like a pretty common case ... someone loses their session, doesn't realize it, and is wondering why they don't get a response to a Logon / connection gets closed. Internally there's a log about the sequence number being too low, but it would be nice to provide that feedback to the other side.
Is there a strong reason why this isn't handled in logon_state.go? Would it be OK to return a rejection of some sort with the information that's logged? (Suggestions on how to best do that, or a different approach are most welcome.)
The text was updated successfully, but these errors were encountered:
This calls verify(logon, false, true), i.e. checkTooHigh = false, checkTooLow = true. In doTargetTooLow, it will call generateLogout() with the error about the MsgSeqNum being too low, which in turn will just send a Logout (5) message.
I suspect that returning logoutState{} in the targetTooLow case should be enough to generate this.
This seems like a pretty common case ... someone loses their session, doesn't realize it, and is wondering why they don't get a response to a Logon / connection gets closed. Internally there's a log about the sequence number being too low, but it would be nice to provide that feedback to the other side.
Is there a strong reason why this isn't handled in logon_state.go? Would it be OK to return a rejection of some sort with the information that's logged? (Suggestions on how to best do that, or a different approach are most welcome.)
The text was updated successfully, but these errors were encountered: