Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Implemented
-
None
-
None
Description
When querying connection history, there are several disparate endpoints that are used to gather that history. Instead of maintaining these various interfaces, we should standardize on a single connection history endpoint and update all of the relevant REST calls within the AngularJS application to reference those calls.
Attachments
Issue Links
- causes
-
GUACAMOLE-1366 Connection-specific history sorted in wrong order
- Resolved