Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Proxying RTC with non-standard URL

Hi,

I realise this question has been asked before here, however there doesn't seem to be a solution to this specific problem.

We are currently using Apache as a reverse proxy for our RTC installation, which simply forwards all requests for the /jazz url to our RTC installation.

We are now looking to put our test instance of RTC (on a different server) behind the same proxy. To do this I have tried adding a new rule to forward all requests for say /jazz2 to the RTC test instance. I have also changed the public URI property on the test instance to be https://<proxy>/jazz2 (and restarted after changing it).


ProxyPass /jazz2/ https://<server>/jazz/
ProxyPassReverse /jazz2/ https://<server>/jazz/


When I try requesting the /jazz2 URL the login page loads, however after pressing the login button I get stuck on the loading screen. Looking at the Apache access logs I can see that although the initial request goes to the /jazz2 URL, the application is still making request to /jazz.


[10/Nov/2010:17:29:43 +0000] "GET /jazz2/ HTTP/1.1"
[10/Nov/2010:17:29:43 +0000] "GET /jazz2/authenticated/identity?redirectPath=%2Fjazz%2F HTTP/1.1"
[10/Nov/2010:17:29:43 +0000] "GET /jazz/web/_style/-3094355420/DMAnApBgBSBTBQBUBRC_DEBlBmC0?importDojoCSS=true HTTP/1.1"
[10/Nov/2010:17:29:43 +0000] "GET /jazz/web/_js/en_GB/-3896583038/QB HTTP/1.1"


Why is RTC still looking for resources at the default URL, and not following the public URI property? What can I do to correct it?

If its relevant, the test server is running RTC 2.0.0.2 (no iFixes).

Thanks

0 votes


Accepted answer

Permanent link
This sort of proxying can be done, but the easiest way to accomplish it is to change the context root of the second Jazz server to be /jazz2 as well. You would need to rename the .war file in tomcat, and renamed the 'jazz' directory in 'conf' to be 'jazz2'. After configuring your second server to respond to requests on /jazz2 without the proxy, adding the proxy is straightforward.

Hi,

We are now looking to put our test instance of RTC (on a different server) behind the same proxy. To do this I have tried adding a new rule to forward all requests for say /jazz2 to the RTC test instance. I have also changed the public URI property on the test instance to be https://<proxy>/jazz2 (and restarted after changing it).


ProxyPass /jazz2/ https://<server>/jazz/
ProxyPassReverse /jazz2/ https://<server>/jazz/


When I try requesting the /jazz2 URL the login page loads, however after pressing the login button I get stuck on the loading screen. Looking at the Apache access logs I can see that although the initial request goes to the /jazz2 URL, the application is still making request to /jazz.


[10/Nov/2010:17:29:43 +0000] "GET /jazz2/ HTTP/1.1"
[10/Nov/2010:17:29:43 +0000] "GET /jazz2/authenticated/identity?redirectPath=%2Fjazz%2F HTTP/1.1"
[10/Nov/2010:17:29:43 +0000] "GET /jazz/web/_style/-3094355420/DMAnApBgBSBTBQBUBRC_DEBlBmC0?importDojoCSS=true HTTP/1.1"
[10/Nov/2010:17:29:43 +0000] "GET /jazz/web/_js/en_GB/-3896583038/QB HTTP/1.1"


Why is RTC still looking for resources at the default URL, and not following the public URI property? What can I do to correct it?

If its relevant, the test server is running RTC 2.0.0.2 (no iFixes).

Thanks
Jared Russell selected this answer as the correct answer

1 vote


One other answer

Permanent link
Hi Matt,

Thanks for the solution it worked perfectly. I did try changing the context root the other day, however I didn't know that you also have to rename the config folder.

Thanks again,

Jared


This sort of proxying can be done, but the easiest way to accomplish it is to change the context root of the second Jazz server to be /jazz2 as well. You would need to rename the .war file in tomcat, and renamed the 'jazz' directory in 'conf' to be 'jazz2'. After configuring your second server to respond to requests on /jazz2 without the proxy, adding the proxy is straightforward.

Hi,

We are now looking to put our test instance of RTC (on a different server) behind the same proxy. To do this I have tried adding a new rule to forward all requests for say /jazz2 to the RTC test instance. I have also changed the public URI property on the test instance to be https://<proxy>/jazz2 (and restarted after changing it).


ProxyPass /jazz2/ https://<server>/jazz/
ProxyPassReverse /jazz2/ https://<server>/jazz/


When I try requesting the /jazz2 URL the login page loads, however after pressing the login button I get stuck on the loading screen. Looking at the Apache access logs I can see that although the initial request goes to the /jazz2 URL, the application is still making request to /jazz.


[10/Nov/2010:17:29:43 +0000] "GET /jazz2/ HTTP/1.1"
[10/Nov/2010:17:29:43 +0000] "GET /jazz2/authenticated/identity?redirectPath=%2Fjazz%2F HTTP/1.1"
[10/Nov/2010:17:29:43 +0000] "GET /jazz/web/_style/-3094355420/DMAnApBgBSBTBQBUBRC_DEBlBmC0?importDojoCSS=true HTTP/1.1"
[10/Nov/2010:17:29:43 +0000] "GET /jazz/web/_js/en_GB/-3896583038/QB HTTP/1.1"


Why is RTC still looking for resources at the default URL, and not following the public URI property? What can I do to correct it?

If its relevant, the test server is running RTC 2.0.0.2 (no iFixes).

Thanks

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Nov 10 '10, 1:55 p.m.

Question was seen: 3,965 times

Last updated: Nov 10 '10, 1:55 p.m.

Confirmation Cancel Confirm