summaryrefslogtreecommitdiffstats
path: root/docs/manual/mod/mod_proxy_connect.xml
diff options
context:
space:
mode:
authorFabien Coelho <fabien@apache.org>2015-01-01 14:56:40 +0100
committerFabien Coelho <fabien@apache.org>2015-01-01 14:56:40 +0100
commitfa1cfae378c950e2d185ed12ef7049f7cadef3d1 (patch)
tree0577ace78ea732df2ac73b4e88b988fa6e0e025a /docs/manual/mod/mod_proxy_connect.xml
parentRegenerate xforms after s/2014/2015/ (diff)
downloadapache2-fa1cfae378c950e2d185ed12ef7049f7cadef3d1.tar.xz
apache2-fa1cfae378c950e2d185ed12ef7049f7cadef3d1.zip
Add a hint about how CONNECT-method requests are filtered out by <Proxy>,
and how to enable them. I could not find this information easily. In particular, the straightforward <Proxy https://www.example.com>... does not allow CONNECT to the corresponding SSL server. Probably it would work if a web client sent a "GET https://www.example.com/ HTTP/1.1" to the proxy, but none would do that. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1648846 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to '')
-rw-r--r--docs/manual/mod/mod_proxy_connect.xml13
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/manual/mod/mod_proxy_connect.xml b/docs/manual/mod/mod_proxy_connect.xml
index 01761f2cef..76bf8b4194 100644
--- a/docs/manual/mod/mod_proxy_connect.xml
+++ b/docs/manual/mod/mod_proxy_connect.xml
@@ -63,6 +63,19 @@
<dt>proxy-source-port</dt>
<dd>The local port used for the connection to the backend server.</dd>
</dl>
+
+ <p>CONNECT method requests are controlled by the
+ <directive module="mod_proxy">Proxy</directive> block
+ as any other HTTP request going through.
+ SSL connections through a proxy may be filtered explicitely
+ by specifying the target host and port, for instance:
+ </p>
+
+ <highlight language="config">
+&lt;Proxy www.example.com:443&gt;
+ Require ip 192.168.0.0/16
+&lt;/Proxy&gt;
+ </highlight>
</section>
<directivesynopsis>