中文标题【使用 Apache 和 mod_proxy】
Atlassian 应用允许用户使用反向代理,但是 Atlassian 并不会为这个功能的配置提供支持。因此,Atlassian 也不能保证能够为这些配置提供任何支持。
如果你在配置上有任何需求,请参考 Atlassian Answers 中的内容来获取帮助。
基本配置
在这些示例中,我们使用下面的信息:
http://www.example.com/confluence - 你计划使用的 URL
http://example:8090/ - Confluence 当前安装的主机名和端口
http://example:8091/ - Synchrony 当前安装的主机名和端口,这个服务被用来提供默认的协同编辑服务
/confluence - 这个是有关你 Confluence 计划使用的上下文(在主机名和端口的后面)
/synchrony - Synchrony 使用的上下文路径,这个提供了协同编辑服务
你需要将上面的 URL 替换成你自己的 URL。
1 设置上下文路径
If you want to access Confluence without a context path, such as www.example.com, skip this step.
Set your Confluence application path (the part after hostname and port) in Tomcat. In this example the context path will be /confluence
.
Edit <installation-directory>conf/server.xml
, locate the "Context" definition:
<Context path="" docBase="../confluence" debug="0" reloadable="true">
and change it to:
<Context path="/confluence" docBase="../confluence" debug="0" reloadable="true">
In this example we've used /confluence
as the context path. Note that you can't use /resources
as your context path, as this is used by Confluence, and will cause problems later on.
Restart Confluence, and check you can access it at http://example:8090/confluence.
2 设置 URL 重定向
Next, set the URL for redirection. In the same <installation-directory>conf/server.xml
file, use the example connectors as a starting point.
Comment out the default connector (for unproxied access).
Uncomment the connector listed under the HTTP - Proxying Confluence via Apache or Nginx over HTTP heading.
Insert your proxyName and proxyPort as shown in the last line below:
<Connector port="8090" connectionTimeout="20000" redirectPort="8443" maxThreads="48" minSpareThreads="10" enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="http" proxyName="www.example.com" proxyPort="80"/>
If you plan to enable HTTPS, use the connector under HTTPS - Proxying Confluence via Apache or Nginx over HTTPS.
3 配置 mod_proxy
Use one of the examples below to edit your Apache http.conf
file to proxy requests to the application server.
You will need to enable the following required Apache modules if they are not already enabled:
- mod_proxy
- mod_proxy_http
- proxy_wstunnel
- mod_rewrite
(proxy_wstunnel and mod_rewrite are new requirements in Confluence 6.0)
The format of the http.conf
file, and location of the modules may differ on your operating system. We recommend Windows users specify the absolute path to the module files.
Example 1: Configuration with context path
Use this example if you set a context path in step 1, and will access Confluence with a context path like this http://www.example.com/confluence.
In this example, users will connect to Synchrony, which is required for collaborative editing, directly via WebSockets.
The order of directives in the config is important.
# Put this after the other LoadModule directives LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so LoadModule proxy_wstunnel_module /usr/lib/apache2/modules/mod_proxy_wstunnel.so LoadModule rewrite_module /usr/lib/apache2/modules/mod_rewrite.so # Put this in the main section of your configuration (or virtual host, if using Apache virtual hosts) ProxyRequests Off ProxyPreserveHost On <Proxy *> Require all granted </Proxy> ProxyPass /synchrony http://<domain>:8091/synchrony <Location /synchrony> Require all granted RewriteEngine on RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC] RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC] RewriteRule .* ws://<domain>:8091%{REQUEST_URI} [P] </Location> ProxyPass /confluence http://<domain>:8090/confluence ProxyPassReverse /confluence http://<domain>:8090/confluence <Location /confluence> Require all granted </Location>
Note: It's not possible to use Apache HTTP Server 2.2 with Confluence 6.0 or later. If you plan to use SSL, you will need version 2.4.10 or later.
Example 2: Configuration without context path
Use this example if you skipped step 1, and will access Confluence without a context path like this http://www.example.com.
As in the previous example, users will connect to Synchrony, which is required for collaborative editing, directly via WebSockets.
The order of directives in the config is important.
# Put this after the other LoadModule directives LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so LoadModule proxy_wstunnel_module /usr/lib/apache2/modules/mod_proxy_wstunnel.so LoadModule rewrite_module /usr/lib/apache2/modules/mod_rewrite.so # Put this in the main section of your configuration (or virtual host, if using Apache virtual hosts) ProxyRequests Off ProxyPreserveHost On RewriteEngine On RewriteCond %{REQUEST_URI} !^/synchrony RewriteRule ^/(.*) http://<domain>:8090/$1 [P] <Proxy *> Require all granted </Proxy> ProxyPass /synchrony http://<domain>:8091/synchrony <Location /synchrony> Require all granted RewriteEngine on RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC] RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC] RewriteRule .* ws://<domain>:8091%{REQUEST_URI} [P] </Location> ProxyPass / http://<domain>:8090 ProxyPassReverse / http://<domain>:8090 <Location /> Require all granted </Location>
Note: It's not possible to use Apache HTTP Server 2.2 with Confluence 6.0 or later. If you plan to use SSL, you will need version 2.4.10 or later.
4 重启 Apache
This is needed to pick up on the new configuration. To restart Apache, run the following command:
sudo apachectl graceful
5 禁用 HTTP 压缩
Having compression run on both the proxy and Tomcat can cause problems integrating with other Atlassian applications, such as Jira. Please disable HTTP compression as per our Using Apache with mod_proxy docs.
6 修改 Confluence 基础 URL
The last stage is to set the Base URL to the address you're using within the proxy, for example http://www.example.com/confluence.
添加 SSL
If you plan to enable HTTPS, see Using Apache with mod_proxy, and make sure you choose the HTTPS sample connector.
更多信息
- The mod_proxy_html site has documentation and examples on the use of this module in the complex configuration.
- Apache Week has a tutorial that deals with a complex situation involving two applications and ProxyHTMLURLMap.