Author: woonsan
Date: Thu Nov 5 17:08:52 2009
New Revision: 833083
URL:
http://svn.apache.org/viewvc?rev=833083&view=revLog:
Refines reverse proxy configurations
Modified:
portals/site/applications/src/site/xdoc/webcontent/index.xml
Modified: portals/site/applications/src/site/xdoc/webcontent/index.xml
URL:
http://svn.apache.org/viewvc/portals/site/applications/src/site/xdoc/webcontent/index.xml?rev=833083&r1=833082&r2=833083&view=diff==============================================================================
--- portals/site/applications/src/site/xdoc/webcontent/index.xml (original)
+++ portals/site/applications/src/site/xdoc/webcontent/index.xml Thu Nov 5 17:08:52 2009
@@ -429,13 +429,25 @@
</p>
<p>
Here are full descriptions for configuration properties.
- <br/>
+ </p>
+ <p>
+ <em>
+ Tip #1: Variables, which are previously defined, can be expanded when the configuration has
+ the variable references wrapped by '${' and '}' like the following example:
+ <source><![CDATA[
+my.cookie.policy = netscape
+proxy.http.client.param.cookiePolicy = ${my.cookie.policy}
+ ]]></source>
+ </em>
<em>
- Note: The previously defined property variables are automatically expanded when the configuration has
- the variable references wrapped by '${property.name}' like the following example:
+ Tip #2: String array typed configuration variables can be defined in one comma separated line or in multiple lines.
+ The following two examples are equivalent each other:
+ <source><![CDATA[
+proxy.reverse.pass.site1.response.cookie.path.rewrite.include = JSESSIONID, PHPSESSIONID
+ ]]></source>
<source><![CDATA[
-defaults.parserAdaptor.html = org.apache.portals.applications.webcontent.rewriter.html.neko.NekoParserAdaptor
-proxy.reverse.pass.somewhere.rewriter.parserAdaptor.html = ${defaults.parserAdaptor.html}
+proxy.reverse.pass.site1.response.cookie.path.rewrite.include = JSESSIONID
+proxy.reverse.pass.site1.response.cookie.path.rewrite.include = PHPSESSIONID
]]></source>
</em>
<table>
@@ -487,16 +499,6 @@
</td>
</tr>
<tr>
- <td>proxy.http.route</td>
- <td></td>
- <td>apache, portals</td>
- <td>
- The comma delimited HTTP route names. Each route name should be used
- in the following configuration properties to set detailed http connection options
- for each route.
- </td>
- </tr>
- <tr>
<td>proxy.http.route.<routename>.target.hostname</td>
<td></td>
<td>portals.apache.org</td>
@@ -635,16 +637,6 @@
</td>
</tr>
<tr>
- <td>proxy.reverse.pass</td>
- <td></td>
- <td>apache, portals</td>
- <td>
- The comma delimited path names for reverse proxy mappings.
- Each path name should be used in the following configuration properties
- to set detailed reverse proxy path mappings.
- </td>
- </tr>
- <tr>
<td>proxy.reverse.pass.dynamicProxyPathMapperCacheCount</td>
<td>1000</td>
<td>2000</td>
@@ -855,6 +847,35 @@
The default request cookies which are sent to the target remote url.
</td>
</tr>
+ <tr>
+ <td>proxy.reverse.pass.<pathname>.response.cookie.path.rewrite.include</td>
+ <td></td>
+ <td>
+ JSESSIONID, PHPSESSIONID
+ </td>
+ <td>
+ <pathname> should be replaced by the real path name.
+ With this example, you may use 'apache' or 'portals' for <pathname>.
+ <br/>
+ The cookies which should have rewritten paths.
+ By default, every cookie path is rewritten if there's no inclusion/exclusion configuration.
+ </td>
+ </tr>
+ <tr>
+ <td>proxy.reverse.pass.<pathname>.response.cookie.path.rewrite.exclude</td>
+ <td></td>
+ <td>
+ CUSTOM1, CUSTOM2
+ </td>
+ <td>
+ <pathname> should be replaced by the real path name.
+ With this example, you may use 'apache' or 'portals' for <pathname>.
+ <br/>
+ The cookies which should have the original path as provided by the target web site.
+ If a cookie name is configured as an exclusion one, then the path of the cookie is not rewritten.
+ By default, every cookie path is rewritten if there's no inclusion/exclusion configuration.
+ </td>
+ </tr>
</table>
</p>
</subsection>
@@ -868,3 +889,4 @@
</body>
</document>
+
