xpra icon
Bug tracker and wiki

Changes between Initial Version and Version 1 of Ticket #1714, comment 4


Ignore:
Timestamp:
12/05/17 11:58:50 (3 years ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1714, comment 4

    initial v1  
    1 {{{
    2 Having looked at it, the only non-relative URL I could find was the favicon (changed in r17566). This would not have caused any problems on its own.
    3 Is there anything else that requires patching?
    4 }}}
     1> Having looked at it, the only non-relative URL I could find was the favicon (changed in r17566). This would not have caused any problems on its own.
     2> Is there anything else that requires patching?
     3
    54
    65There only issue here is proxying. XPRA being served at the relative path will proxy a request to XPRA with that relative path, so, for example, if XPRA is being served at /xpra-application-1, then the XPRA web server will receive an HTTP GET for /xpra-application-1, which will result in a 404 because the path is served at the root. It would be great if the actual path ere could be configurable.
    76
    8 {{{
    9 This could be done even more easily with ​apache requestheader and r17567: just pass an extra request attribute of path=thepathyouwant to the client's index page and it will use that.
    10 }}}
    11 
     7> This could be done even more easily with ​apache requestheader and r17567: just pass an extra request attribute of path=thepathyouwant to the client's index page and it will use that.
    128Appending query strings to the URL to specify web socket path is totally fine with me. Yes, I am aware that proxying will cause some performance reduction but we need to tie this into Harvard CAS/SAML authentication and the proxy I wrote does this. So far I've been using it this way and it performs pretty well!
    13 
    14 
    15 
    16