When infoscreen3 was placed behind a https terminating front proxy, websocket implementation did not work as expected due to port mapping and protocol issues. These problems come from having port and protocol hard coded to the source code that generates the necessary templates. This patch addresses those problems by making it possible to tell infoscreen3 that it is behind a proxy and server url should be handled in a different manner without hardcoding the port and forcing protocol to be https everywhere.
reaby
commented
2 years ago
When infoscreen3 was placed behind a https terminating front proxy, websocket implementation did not work as expected due to port mapping and protocol issues. These problems come from having port and protocol hard coded to the source code that generates the necessary templates. This patch addresses those problems by making it possible to tell infoscreen3 that it is behind a proxy and server url should be handled in a different manner without hardcoding the port and forcing protocol to be https everywhere.