(mod/mod_proxy_express.xml)
It does more than just a ProxyPass, but also looks at the HOST header,
so this gives somewhat deeper insight into what the end result looks
like.
(mod/mod_proxy_connect.xml)
a comma leaked onto the page
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@
1598284 13f79535-47bb-0310-9956-
ffa450edef68
requests, <module>mod_proxy</module> and
<module>mod_proxy_connect</module> have to be present in the server.</p>
- <p>CONNECT is also used, when the server needs to send an HTTPS request
+ <p>CONNECT is also used when the server needs to send an HTTPS request
through a forward proxy. In this case the server acts as a CONNECT client.
This functionality is part of <module>mod_proxy</module> and
<module>mod_proxy_connect</module> is not needed in this case.</p>
<li>It does not support regex or pattern matching at all.
</li>
<li>It emulates:
- <example>
- ProxyPass / backend.server:port<br />
- ProxyPassReverse / backend.server:port<br />
- </example>
+ <highlight language="config">
+<VirtualHost *:80>
+ ServerName front.end.server
+ ProxyPass / back.end.server:port
+ ProxyPassReverse / back.end.server:port
+</VirtualHost>
+ </highlight>
That is, the entire URL is appended to the mapped backend
URL. This is in keeping with the intent of being a simple
but fast reverse proxy switch.