Ticket #423: Fix mod_proxy docs regarding ProxyPassReverse.
diff --git a/src/chapters/installing.xml b/src/chapters/installing.xml
index 4c058cd..5508976 100644
--- a/src/chapters/installing.xml
+++ b/src/chapters/installing.xml
@@ -813,7 +813,7 @@
Order allow,deny
Allow from all
ProxyPass ajp://<replaceable>HOSTNAME</replaceable>:<replaceable>8009</replaceable>/guacamole/ max=20 flushpackets=on
- ProxyPassReverse ajp://<replaceable>HOSTNAME</replaceable>:<replaceable>8009</replaceable>/guacamole/
+ ProxyPassReverse <replaceable>http://HOSTNAME</replaceable>/guacamole/
</Location></programlisting>
</informalexample>
<para>The most important thing in this entire section is the option
@@ -824,6 +824,12 @@
buffering this stream breaks Guacamole's communication.</para>
<para><emphasis>If the option <option>flushpackets=on</option> is not specified,
Guacamole will not work</emphasis>.</para>
+ <para>Note also the protocol of the URL specified in the
+ <parameter>ProxyPassReverse</parameter> directive. The protocol
+ <emphasis>MUST</emphasis> match the protocol that will be used to connect to
+ to Apache. The example above specifies <replaceable>http</replaceable>, but if
+ you are using HTTPS then the URL specified here will have to reflect
+ this.</para>
</section>
</section>
<section xml:id="http-proxy">
@@ -915,7 +921,7 @@
Order allow,deny
Allow from all
ProxyPass ajp://<replaceable>HOSTNAME</replaceable>:<replaceable>8009</replaceable>/guacamole/ max=20 flushpackets=on
- ProxyPassReverse ajp://<replaceable>HOSTNAME</replaceable>:<replaceable>8009</replaceable>/guacamole/
+ ProxyPassReverse <replaceable>http://HOSTNAME</replaceable>/guacamole/
ProxyPassReverseCookiePath /guacamole/ <replaceable>/new-path/</replaceable>
</Location></programlisting>
</informalexample>
@@ -925,6 +931,10 @@
instructing <package>mod_proxy</package> to update the cookie path, changing
<uri>/guacamole/</uri> to <uri>/new-path/</uri>, the same path specified when
the location was declared.</para>
+ <para>Be careful when specifying the URL in the <parameter>ProxyPassReverse</parameter>
+ directive. The protocol or the URL <emphasis>MUST</emphasis> match the protocol that
+ will be used to connect to to Apache, even if it differs from the protocol being
+ used to connect to Tomcat.</para>
</section>
</section>
</chapter>