Open renaudboyer opened 2 years ago
According to this issue the broken session problem is already solved in case idle in this PR https://github.com/linagora/customers/issues/51
So normally the case of websocket disconnection due to broken session is to be avoided
I tested the idle session case on the different environment to reproduce the websocket disconnection bug
Current behaviour : the token expire when getting user information see the demo for more details
Expected behaviour: When the silent refresh not succeed the application will be redirected to login page
Theoretically this PR should handle our problem, if the token expires and we code 401, the sign must be done https://github.com/linagora/esn-frontend-common-libs/pull/234/files#
Current Behaviour : The websocket still connected in idle session see the the demo for more details
Problem: External event will not be added in real time (example : with google calendar)
TODO list: check websocket ping settings and time to live of the backend and intermediate proxies.
When keeping calendar web app opened for a long time, push updates don't work anymore and user display does not show latest updates or invitations on calendar view.
The push update system is using websocket and over time, websocket get disconnected.
Criteria