From: Rich Bowen Date: Tue, 26 Jun 2012 16:20:25 +0000 (+0000) Subject: Applying patch from PR 53201 X-Git-Tag: 2.2.23~147 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f52ed996ea46bfdb59084957e8bb28c847fc87f9;p=thirdparty%2Fapache%2Fhttpd.git Applying patch from PR 53201 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1354090 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml index e6e5c4e92e5..eee3af85dad 100644 --- a/docs/manual/mod/mod_proxy.xml +++ b/docs/manual/mod/mod_proxy.xml @@ -555,6 +555,9 @@ request need also mod_proxy_http or mod_proxy_ftp (or both) present in the server.

+

In order to get the functionality of proxying HTTPS sites, you + need mod_proxy_connect enabled in the server.

+ Warning

Do not enable proxying with ProxyRequests until you have VirtualHost section to enable SSL/TLS for proxy usage in a particular virtual host. By default the SSL/TLS Protocol Engine is disabled for proxy image both for the main server and all configured virtual hosts.

+ +

Note that the SSLProxyEngine directive should not, in +general, be included in a virtual host that will be acting as a +forward proxy (using <Proxy> or <ProxyRequest> directives. +SSLProxyEngine is not required to enable a forward proxy server to +proxy SSL/TLS requests.

+ Example <VirtualHost _default_:443>
SSLProxyEngine on