How can I change the port 9991 (SSL) to just using 443? We don’t want the port to have to be part of the URL.
Paul,
Currently the Percussion application is unable to run over port 443. If you would prefer not to expose non-standard ports, one option would be to proxy to the CMS’s HTTP port 9992 by way of HTTPS port 443 using an IIS or Apache front-end server (you would need to relocate your SSL cert to one of these servers to enable HTTPS on them).
For example, using IIS, you could essentially follow step 3 of this doc:
http://help.percussion.com/admin-topi…
But you would be performing these actions on the application server, and your single rule would look like this:
Name: Percussion CMS
Pattern: (.*)
Rewrite URL: http://localhost:9992/{R:1}
Then you users could securely connect to the application server over HTTPS port 443, and the connection would be internally rerouted to port 9992. Let me know if this will work in your case.
Hrmm, okay. Thanks. I’ll take the information to our Networking department and see what they say…
any performance hits by routing this way?
If any, it would be very minimal, as this would be a local proxy (so the connection is not being bounced from server to server, etc.).