RELEASED: Public: October 30, 2024
Resolved issues
- Fix reverse proxy support for configurations terminating TLS at the controller level (BEE-52299)
-
Previously, an exception would occur in the following scenarios:
-
When terminating TLS at controller level (controller started with
-httpsPort=…) -
When browsing a running build in a replica other than the one the user is tied to via a sticky session
-
- When terminating TLS at the controller level, websocket agents could not roam between replicas (BEE-52300)
-
In a High Availability (HA) setup, when terminating TLS at the controller level, websocket agents connect to a single replica. However, when there is a running build that requires this agent, a replica might reverse proxy the websocket connection to another one and this would fail.
This issue has been addressed and this use case will work as expected.