Posted by npujol73 on
URL: https://discuss.orbeon.com/Versioned-resources-in-separate-deployment-tp1574338p1576044.html

Thanks for your reply Alex. I now realize that my question was unclear/confusing. I apologize for that. Your point about versioned resources makes sense and was my understanding.

My issue is more around determining what the urls to images/servlets/javascript/css should be in a separate deployment if I host that content in my own war along with some xml producing servlets that feed a couple of xforms:instances.

 This gets particularly confusing in a proxied environment where it appears that making urls relative is just not enough (since i presume httpclient connections to some of the resources may be opened and a fully qualified url is needed to do so). In my situation our app server servers multiple host names. For example:

http://demo1.home.com/
http://demo2.home.com/

In addition the web exposed port (80) is different than the one the server is actually running on the box itself (8080). I have  used the url-rewriting properties successfully but it is not ideal for me since the hostname really depends on the url that solicited the xform in the first place and that could be any of demo1.home.com or demo2.home.come (localhost or a generic hostname is not an option because the app server uses the hostname to drive some logic that determine what content will be served e.g http://demo1.home.com/ctx/images/mygif and http://demo2.home.com/ctx/images/mygif serve different content).

 I have seen there is also a proxy.port / proxy.host property and I was hoping to use JUST the port property with the thought that by default the hostname would be obtained from the request that solicited the xform in the first place - but that does not seem to work. Any thoughts?

Does that all make sense?