module: web_dialog_size
version: all
Steps to reproduce
- Log in to an account in browser 1
- Log in to the same account in browser 2
- In browser 2, change the password of the user (this invalidates other sessions)
- Return to browser 1 and interact with the UI (e.g., click anywhere)
- Observe network activity in the browser dev tools
Current behavior
When the session is invalidated, the frontend continuously triggers failing RPC calls. This results in an infinite loop of rejected promises, causing repeated requests to the server and potentially leading to excessive load (self-DDoS-like behavior).
Expected behavior
When the session is invalid or expired, failed RPC calls should be handled gracefully. The frontend should stop retrying automatically and avoid repeated requests, preventing unnecessary load on the server and ensuring stable behavior.
I have gone ahead and written the following PR: #3523
module: web_dialog_size
version: all
Steps to reproduce
Current behavior
When the session is invalidated, the frontend continuously triggers failing RPC calls. This results in an infinite loop of rejected promises, causing repeated requests to the server and potentially leading to excessive load (self-DDoS-like behavior).
Expected behavior
When the session is invalid or expired, failed RPC calls should be handled gracefully. The frontend should stop retrying automatically and avoid repeated requests, preventing unnecessary load on the server and ensuring stable behavior.
I have gone ahead and written the following PR: #3523