ThinLinc specific information

When a user starts a session, the master redirects the client to a specific path in the format /connect/<agent identifier>/. This identifier is determined by the /vsmagent/agent_hostname (or the agent’s IP if unset). The proxy must capture this path to correctly route the traffic to the agent service.

Note

In a scenario where a large number of simultaneous ThinLinc sessions are directed through a single reverse proxy, the reverse proxy might become a network bottleneck. In such cases, make sure to take ThinLinc’s bandwidth requirements into account in your reverse proxy architecture.