Details
-
Suggestion
-
Resolution: Unresolved
-
None
Description
The documentation around configuring tomcat inside JIRA when JIRA is running behind a web server or proxy that handles https:// for JIRA is not as complete as it should be and some customers are ending up with a non-optimal configuration. This seems to be due to information about setting the appropriate attributes of the tomcat Connector element found <JIRA_INSTALL>/conf/server.xml (secure should be set to true and updating the scheme, proxyName & proxyPort as well as per https://confluence.atlassian.com/jira/integrating-jira-with-apache-using-ssl-203395380.html needs to be done appropriately) not being present on the information for using a proxy (or Apache) in front of JIRA on pages such as https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html .
Attachments
Issue Links
- relates to
-
JRASERVER-35409 The xsrf cookie token is not a 'secure' cookie for secure('https') requests
- Closed
-
GHS-90030 Loading...