Using Apache with mod_jk
Proxy and HTTPS setup for Confluence
- Configuring Web Proxy Support for Confluence
- Connecting to LDAP or Jira applications or Other Services via SSL
- Using Apache with mod_proxy
- Running Confluence behind NGINX with SSL
- Running Confluence Over SSL or HTTPS
- Using Apache to limit access to the Confluence administration interface
- Using Apache with mod_jk
- Using mod_rewrite to Modify Confluence URLs
On this page
Related content
- Creating issues and sub-tasks
- How to automatically transition parent linked issue when all child linked issues in the same status using Automation
- Create issues and sub-tasks
- Automation Rule Not Updating Cascade Field Correctly
- Creating issues using the CSV importer
- Cannot delete an issue type and unable to find issues associated to a deleted issue type
- Moving an issue
- Configuring sub-tasks
- Adding, editing, and deleting an issue type
It's not possible to use only mod_jk to proxy Confluence 6.0 or later. This is because Synchrony, which is required for collaborative editing, cannot accept AJP connections. The preferred configuration is Using Apache with mod_proxy.
If you are unable to switch to mod_proxy, see [ARCHIVED] How to configure Apache mod_jk to proxy Confluence 6.x or later for a workaround.
Last modified on Nov 1, 2017
Related content
- Creating issues and sub-tasks
- How to automatically transition parent linked issue when all child linked issues in the same status using Automation
- Create issues and sub-tasks
- Automation Rule Not Updating Cascade Field Correctly
- Creating issues using the CSV importer
- Cannot delete an issue type and unable to find issues associated to a deleted issue type
- Moving an issue
- Configuring sub-tasks
- Adding, editing, and deleting an issue type
Powered by Confluence and Scroll Viewport.