Bug 5394 - difficult to use tlwebaccess/tlwebadm behind reverse proxy that modifies urls
Summary: difficult to use tlwebaccess/tlwebadm behind reverse proxy that modifies urls
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
: 5678 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-01-07 16:07 CET by Samuel Mannehed
Modified: 2024-11-20 23:43 CET (History)
5 users (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Samuel Mannehed cendio 2015-01-07 16:07:11 CET 
Currently you access these services from https://<yourthinlincserver>:<port> and don't have any option if you would like to run these services in a subdirectory. Example:

https://example.com:300/thinlinc

instead of 

https://example.com:300

This could be achieved by either a configuration parameter or by having the services figure out their prefix path and then using relative paths in the code.
Comment 2 Pierre Ossman cendio 2018-03-13 15:49:09 CET 
This scenario only happens with a proxy, so we don't need to have explicit support for this in ThinLinc. We just need to make sure we don't break the proxy's rewriting of URLs. If we start using relative URLs everywhere then things should be fine without any extra logic.
Comment 3 Pierre Ossman cendio 2018-05-15 13:27:18 CEST 
*** Bug 5678 has been marked as a duplicate of this bug. ***
Comment 4 Pierre Ossman cendio 2018-05-15 13:31:13 CEST 
It's actually possible to get this working, but it requires a lot of configuration in the proxy to rewrite all the URLs correctly. And these are internal aspects of ThinLinc so they are difficult for the administrator to keep an eye on.

Here is one guide a user has written to do this:

https://www.verboom.net/blog/index.html?single=20151019.0
Comment 9 Pierre Ossman cendio 2022-04-22 10:12:23 CEST 
The biggest issue is the redirection from the master to the agent. Relative URLs are not possible there, since we are redirecting to a different host.
Note You need to log in before you can comment on or make changes to this bug.