Reverse Proxy Issues

Ben,

You want to unset the wt.webserver.port setting (remove it from your site.xconf)

Setting to https: automatically implies to use the default port :443

Additionally we have discovered that setting the port property causes some WGM workspace issues in a reverse proxy configuration.
Best Regards,
Carsten Lawrenz
Kalypso
Delivering on the Promise of Innovation
m. 415.378.6374

[cid:3FD55945-8CFB-4CD9-AFFF-9B6B04FE08C3@ent.core.medtronic.com]
[cid:B78E2E9B-C7D7-4A08-A293-480B9B2875CC@ent.core.medtronic.com]<[cid:86C63AB6-0EE4-4115-8D50-ECBBD8B6715C@ent.core.medtronic.com]<http: www.facebook.com=" kalypsolp=">[cid:EF7EDB2D-A4C5-4281-B7D2-74374302AB3F@ent.core.medtronic.com]<http: twitter.com=" kalypsolp=">[cid:9B97D2CD-AA56-45FC-9534-D3826FEA9F73@ent.core.medtronic.com]<http: www.linkedin.com=" company=" kalypso=">[cid:7D42E6BC-DCD9-47E1-84D8-A5CBB6E8557A@ent.core.medtronic.com]<http: www.youtube.com=" user=" kalypsolp=">[cid:6EA4D052-5637-4AB9-B39E-C46E0B53A484@ent.core.medtronic.com]">http://kalypso.com/smalljewel>[cid:86C63AB6-0EE4-4115-8D50-ECBBD8B6715C@ent.core.medtronic.com]<http: www.facebook.com=" kalypsolp=">[cid:EF7EDB2D-A4C5-4281-B7D2-74374302AB3F@ent.core.medtronic.com]<http: twitter.com=" kalypsolp=">[cid:9B97D2CD-AA56-45FC-9534-D3826FEA9F73@ent.core.medtronic.com]<http: www.linkedin.com=" company=" kalypso=">[cid:7D42E6BC-DCD9-47E1-84D8-A5CBB6E8557A@ent.core.medtronic.com]<http: www.youtube.com=" user=" kalypsolp=">[cid:6EA4D052-5637-4AB9-B39E-C46E0B53A484@ent.core.medtronic.com]



We have set up our servers to use HTTPS instead of HTTP. We did not change the settings for wt.webserver.port from the default value of 80. Internal users have no issues when using Windchill. Should this port be changed for 443?


When we tried to configure a reverse proxy server, Windchill will display the PTC splash logo and then gives an error that the application cannot be found. One of the settings in the reverse proxy setup changes the wt.server.codebase to point to the external proxy server: /Windchill<https: %3creverse_proxy_server%3e=" windchill=">">https://<reverse_proxy_server>/Windchill<https: %3creverse_proxy_server%3e=" windchill="> is how I have it set. I tried this with and without specifying port 80. If we change the wt.webserver.port, will that work if I also specify port 443 for wt.server.codebase? Also, do the internal user now have to use the external URL for their Windchill sessions or will the system resolve itself if they use their existing URL to the internal server?


The third issues is with the mods to http.conf in Apache on the reverse proxy server. In CS68466, it states that the syntax must be exact and is written like this: ProxyPass /Windchill /Windchill<https: %3cinternal_server%3e=" windchill=">.">https://<internal_server>/Windchill<https: %3cinternal_server%3e=" windchill=">. ProxyPassReverse is the same. In the Advanced Deployment guide, it shows the syntax as: ProxyPass /Windchill/ /Windchill/https://%3cinternal_server%3e/Windchill.">https://<internal_server>/Windchill/https://%3cinternal_server%3e/Windchill. Are the training '/' required or not?