Massage retention policy data sent to the UI
Use some math to determine what intervals have been set
Implement controlling the chart range popup via the available ranges
If you enter invalid credentials and attempt login, you will see the warning popup show. Then, do not close it but log in with valid credentials. The popup remains. You can close it via the "Close" button but this change will remove the popup for you
Fixes#609, reported in rabbitmq/rabbitmq-server#1704
Add new configuration parameter login_session_timeout.
Add login_session_timeout to whoami response.
Use it as an expiration timeout for auth cookie.
[#157940664]
The click handlers for certain elements are being cleared by the `postprocess_partial` function. This change ensures they are restored, but only on elements that are descendents of `.updatable`
Fixes#507
Prior to this change:
Management API returned status code 502: 502 Bad Gateway: Registered endpoint failed to handle the request.
After this change:
Management API returned status code 502 - 502 Bad Gateway: Registered endpoint failed to handle the request.
Validation code in place, how to display?
Take existing queue count into consideration
Server-side validation takes existing queue count into consideration. Improve error message sent back to web application.
Improve messaging, remove unused template
Take existing queues into account when importing definitions for all vhosts. Fix test suite.
* Don't throw and give up when our "pre-pre-prehistoric virtual DOM"
update isn't consistent, reaload instead
* Coerce the input to a string in two formatting functions
* In the same functions, catch nulls and undefined values early
This fixes a couple of relatively difficult to reproduce exceptions
caused by stats emission timing + DOM updates timing
that make the UI dysfunctional.
It was moved to local storage together with personal
preferences (e.g. what columns should be displayed in various
tables) in 8be18652f4 (3.4.0), very unlikely
by design.
This is a short term solution for session expiration. A proper
one would be moving to a token-based system such as OAuth 2.0.
[#142212963]