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
The reason for that is that for example when the method eot() is called, closeConnection() is called directly without calling onClose(). But in onClose() the readystate is changed to closing.
Since closeConnection() is setting the readystate to closed at the end of the method, this is not a real issue, just looks bad.
Expected Behavior
connection is in readystate closing during onWebSocketClose
Current Behavior
connection can be in readystate open during onWebSocketClose e.g. due to end-of-stream error causing a eot() call
Possible Solution
Change the readystate to closing when the readystate is still open and it is a close with CloseFrame.ABNORMAL_CLOSE
Steps to Reproduce (for bugs)
Not needed.
Debug log (for bugs)
Not needed.
Context
Not needed.
Your Environment
Version used: 1.3.7-dev
Java version: 8
Operating System and version: Windows 10
Endpoint Name and version: Firefox
Link to your project:
The text was updated successfully, but these errors were encountered:
This is just a tracking issue!
The reason for that is that for example when the method eot() is called, closeConnection() is called directly without calling onClose(). But in onClose() the readystate is changed to closing.
Since closeConnection() is setting the readystate to closed at the end of the method, this is not a real issue, just looks bad.
Expected Behavior
connection is in readystate closing during onWebSocketClose
Current Behavior
connection can be in readystate open during onWebSocketClose e.g. due to end-of-stream error causing a eot() call
Possible Solution
Change the readystate to closing when the readystate is still open and it is a close with CloseFrame.ABNORMAL_CLOSE
Steps to Reproduce (for bugs)
Not needed.
Debug log (for bugs)
Not needed.
Context
Not needed.
Your Environment
The text was updated successfully, but these errors were encountered: