#1784 closed enhancement (fixed)
Add path parameter to connect page
| Reported by: | Chris Hills | Owned by: | Chris Hills |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.3 |
| Component: | html5 | Version: | trunk |
| Keywords: | Cc: |
Description
Please add a path parameter to the connection page for use when running xpra behind a proxy.
Change History (4)
comment:1 Changed 3 years ago by
| Milestone: | future → 2.3 |
|---|---|
| Status: | new → assigned |
comment:2 Changed 3 years ago by
| Owner: | changed from Antoine Martin to Chris Hills |
|---|---|
| Status: | assigned → new |
comment:3 Changed 3 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I have updated the wiki and removed the ugly hack which is no longer necessary: wiki/Nginx.
Feel free to re-open if I've missed something.
comment:4 Changed 3 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1784
Note: See
TracTickets for help on using
tickets.
copyleft 2010 - 2021
r18725 should be sufficient.
You can place the index.html and connect.html at any path location and that same pathname will be used for the websocket connection to the xpra server, or you can override the location with the "path" parameter which is shown under "advanced options" on the connect page.
If that works for you, we can remove the ugly path hack from wiki/Nginx