"--ws-endpoint" take no effect #127

Activity

1. jourdain commented on May 11, 2023

   

   jourdain

   on May 11, 2023

   Collaborator

   More actions

   This was most-likely an oversight when migrating wslink to v1. But in practice changing that endpoint should not be required.
   For real-world deployment, a pvw process tends to be ran in an internal network with a proxy that rewrite all those url to be session based.
2. yungxiaomcc commented on May 12, 2023

   

   yungxiaomcc

   on May 12, 2023

   Author

   More actions

   I use nginx to forward external request to internal visualizer process with prefix like "proxr/abc/", when opened the url (should be "http://{{host}}:{{port}}/proxr/abc/index.html")，but the ws connection url is wrong which is "ws://{{host}}:{{port}}/ws". Maybe this is cause of front-end building option of "publicPath" (not sure)，so i try to change "ws-endpoint" to make it work. Plz help me out this issue.
3. yungxiaomcc commented on May 12, 2023

   

   yungxiaomcc

   on May 12, 2023

   Author

   More actions

   I use nginx to forward external request to internal visualizer process with prefix like "proxr/abc/", when opened the url (should be "http://{{host}}:{{port}}/proxr/abc/index.html")，but the ws connection url is wrong which is "ws://{{host}}:{{port}}/ws". Maybe this is cause of front-end building option of "publicPath" (not sure)，so i try to change "ws-endpoint" to make it work. Plz help me out this issue.

   I use paraview.apps.trame as running module, it works well in my app.
4. jourdain commented on May 12, 2023

   

   jourdain

   on May 12, 2023

   Last edited by jourdain

   Collaborator

   More actions

   So you don't need to change it via ws-endpoint. Just add that info in the URL like http://{{host}}:{{port}}/proxr/abc/index.html?sessionURL=ws://......

   The way we do the routing with Apache and our launcher is by doing that and having the launcher properly providing that sessionURL internally with the session information.

   Anyway, it seems that you just need to configure your launcher...
5. yungxiaomcc commented on May 12, 2023

   

   yungxiaomcc

   on May 12, 2023

   Author

   More actions

   So you don't need to change it via ws-endpoint. Just add that info in the URL like http://{{host}}:{{port}}/proxr/abc/index.html?sessionURL=ws://......

   The way we do the routing with Apache and our launcher is by doing that and having the launcher properly providing that sessionURL internally with the session information.

   Anyway, it seems that you just need to configure your launcher...

   I have updated my configration as you siad, and it worked. Thanks!