-
Bug
-
Resolution: Fixed
-
Trivial
-
2.4
-
None
-
Security Level: Public
-
None
-
Debian SSL Proxy (Apache) in front of an CentOS box with Jira Standalone 4.2.2 running on an non-official port and path /jira and Minyaa 4.2.0
-
4.2.1
Hi,
As you will see in the screenshots, the links to ShowExtendedTimeTracking, etc. are misleading to
https://dev.konqi.net/secure/ShowExtendedTimeTrackingHelp.jspa?decorator=popup#LogWork
instead of
https://dev.konqi.net/jira/secure/ShowExtendedTimeTrackingHelp.jspa?decorator=popup#LogWork
The jira base-url is set correctly to https://dev.konqi.net/jira too, and Jira is working fine itself since months.
The Plugins-Settings page tells me:
Is your JIRA instance accessible from several URLs. > NO
^setting to Yes won't have any effect
Here is my server.xml changes from Jira
[root@goofy jira-4.2.2]# diff -u ./conf/server.xml.bak ./conf/server.xml
--- ./conf/server.xml.bak 2011-01-30 18:46:44.000000000 +0100
+++ ./conf/server.xml 2011-01-30 18:47:47.000000000 +0100
@@ -61,7 +61,12 @@
useBodyEncodingForURI="true"
redirectPort="8443"
acceptCount="100"
- disableUploadTimeout="true"/>
+ disableUploadTimeout="true"
+
+ proxyName="dev.konqi.net"
+ proxyPort="443"
+ scheme="https"
+ />
<!--
====================================================================================
@@ -115,7 +120,7 @@
<Engine name="Catalina" defaultHost="localhost">
<Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">
- <Context path="" docBase="${catalina.home}/atlassian-jira" reloadable="false" useHttpOnly="true">
+ <Context path="/jira" docBase="${catalina.home}/atlassian-jira" reloadable="false" useHttpOnly="true">
<!--
