I would recommend putting someting in front to do SSL offloading, like Apache2, ngix or varnish (or a StingRay).
This often simplifies the SSL implementation, and makes Confluence upgrades simpler. Also, some extra caching, redirection or URL rewriting can be performed.
For Apache, You can use either mod_proxy or mod_jk... I have this Link that is quite good, its for LifeRay, but thats a Tomcat server also
Yup, one of Dan's standing orders in "The (not so) Dark Art of Performance Tuning of Atlassian apps" is "never terminate SSL at Tomcat, do it in Apache/nginx/varnish etc"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes. Here is some documentation for it.
https://confluence.atlassian.com/display/DOC/Running+Confluence+Over+SSL+or+HTTPS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First hit on most search engines is the atlassian doc for running confluence on SSL
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Again, yes. Read the documentation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.