Weasis Viewer via Reverse Proxy or Router fails after viewer.jnlp

279 views
Skip to first unread message

Rüdiger

unread,
Mar 27, 2013, 6:42:07 AM3/27/13
to dcm...@googlegroups.com
Hi all,

I have a problem using Weasis behind a Reverse Proxy or behind a Linux router. Imagine the scenario:

Client (192.168.1.10) - calls http://192.168.1.20
        |
Router (192.168.1.20): NATs the request to dcm4che-Server at 192.168.9.100
        |
dcm4chee-web3 is located on 192.168.9.100

NATting and http://192.168.9.100/dcm4chee-web3 work fine. No matter if I use a Router with NAT or a Reverse Proxy, the downloaded viewer.jnlp on the client (192.168.1.10) tries to get more components - but hard-coded/absolute from its origin server (192.168.9.100), which fails.

Where do I have to configure Weasis to get its mandatory addons relatively? Or do I have to set a flag somewhere?


Regards

zaka

unread,
Mar 27, 2013, 12:38:58 PM3/27/13
to dcm...@googlegroups.com
Hi!

It's not a good news for me, because I am going to place my PACS behind a firewall. :(
Unfortunately I have no possibility to check this issue right now, but for the first glance weasis-jnlp.xml on the server side already has relative URL ${weasis.base.url} ! And this is a problem, because viewer.jnlp on the client side would contain http://192.168.9.100:8080 as a base URL. Maybe the solution is to put hardcoded NATed (masqueraded) http://192.168.1.20:8080 as a base URL into weasis-jnlp.xml on the server side?

среда, 27 марта 2013 г., 16:42:07 UTC+6 пользователь Rüdiger написал:

nicolas...@gmail.com

unread,
Mar 28, 2013, 3:05:27 AM3/28/13
to
I found a bug in weasis-pacs-connector, the variable ${server.base.url}was set only during the first request. You can try a new version here.

To have a dynamic base URL, you must have weasis-pacs-connector and the WADO server on the same server (this is the case if you follow the default installation of dcm4chee). The configuration must be (it is the default values):
weasis.base.url=${server.base.url}
pacs.wado.url=${server.base.url}/wado

Don't forget to restart dcm4chee after changing these properties.

Otherwise, you can
change the variable by your IP.

Hope it helps

Rüdiger

unread,
Apr 2, 2013, 9:16:08 AM4/2/13
to dcm...@googlegroups.com
Perfect! It works! Thank you very much, unbelievable. :-)
Reply all
Reply to author
Forward
0 new messages