Port number in CLM URL - Yes or No
We are in the planning phase of an „Enterprise Topology“ CLM environment.
One of the discussions in the last weeks was about the URL of the HTTP Reverse Proxy. Our first suggestion was to have a URL like
https://clm_p.xyz.com/ (with the default https port 443).
But then we heard the rumor that it should be better to add the port number to the URL like
https://clm_p.xyz.com:443/
Even IBM consultants have a different opinion about this, but nobody could say why.
Are there any known reasons, why the port number should be in the URL or why not?
3 answers
If you wish to use a different port than the default https port 443, you need to specify the port explicitly.
If you are using port 443, strictly speaking, you can omit the port number, however please note that in older versions of RTC Eclipse client there was a subtle bug appearing under certain conditions, if the port was not explicitly included in the URL
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=189055
This defect is already fixed, so if you are using any recent version of RTC, this should not be a concern for you.
If you are using port 443, strictly speaking, you can omit the port number, however please note that in older versions of RTC Eclipse client there was a subtle bug appearing under certain conditions, if the port was not explicitly included in the URL
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=189055
This defect is already fixed, so if you are using any recent version of RTC, this should not be a concern for you.
Dieter,
the reason why it appears with 9443 is that 9443 is NOT the well known port for HTTPS and the URI has to be set up with providing it explicitly, or else you cant connect.
Disadvantages with other ports as 443 (and thus showing the port) are that you would have allow access to 9443 or other ports explicitly in firewalls.
Please see https://jazz.net/library/article/831 for some ideas.
the reason why it appears with 9443 is that 9443 is NOT the well known port for HTTPS and the URI has to be set up with providing it explicitly, or else you cant connect.
Disadvantages with other ports as 443 (and thus showing the port) are that you would have allow access to 9443 or other ports explicitly in firewalls.
Please see https://jazz.net/library/article/831 for some ideas.
Hi Dieter,
by default, web servers use port 80 for non secure communications (over HTTP) and port 443 for secure communications (over HTTPS). For the "How to" part - i.e. explanation on how to change default port on your server (be it Tomcat or WAS) - , you may want to have a read at this blog post: https://sleroyblog.wordpress.com/2012/03/30/tip-for-jazz-administration-hide-port-numbers-from-the-public-server-uri/
For the configuration of your reverse proxy, the Administration workshop ( https://jazz.net/library/article/831 ) is indeed (that was already pointed out by Ralph) a good pick.
Regards,
Stéphane
by default, web servers use port 80 for non secure communications (over HTTP) and port 443 for secure communications (over HTTPS). For the "How to" part - i.e. explanation on how to change default port on your server (be it Tomcat or WAS) - , you may want to have a read at this blog post: https://sleroyblog.wordpress.com/2012/03/30/tip-for-jazz-administration-hide-port-numbers-from-the-public-server-uri/
For the configuration of your reverse proxy, the Administration workshop ( https://jazz.net/library/article/831 ) is indeed (that was already pointed out by Ralph) a good pick.
Regards,
Stéphane