Httpd mod proxy Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 24: Line 24:
* [[httpd ProxyPassReverseCookieDomain|ProxyPassReverseCookieDomain]]
* [[httpd ProxyPassReverseCookieDomain|ProxyPassReverseCookieDomain]]
* [[httpd ProxyPassReverseCookiePath|ProxyPassReverseCookiePath]]
* [[httpd ProxyPassReverseCookiePath|ProxyPassReverseCookiePath]]
* [[httpd ProxyPassMatch|ProxyPassMatch]]
* [[httpd ProxyPassInherit|ProxyPassInherit]]
* [[httpd ProxyPassInherit|ProxyPassInherit]]
* [[httpd ProxyPassInterpolateEnv|ProxyPassInterpolateEnv]]
* [[httpd ProxyPassInterpolateEnv|ProxyPassInterpolateEnv]]

Revision as of 19:53, 3 January 2017

External

Internal

Secure mod_proxy

TODO

Directives

Forward Proxy Configuration

A forward proxy is activated using the ProxyRequests directive.

Reverse Proxy Configuration

A reverse proxy is activated using the ProxyPass directive or the [P] flag to the RewriteRule directive. It is not necessary to turn ProxyRequests on in order to configure a reverse proxy.

Controlling access to the Proxy

Use the <Proxy> control block:

<Proxy "*">
    Require ip 192.168.0
</Proxy>

mod_proxy mod_cluster Configuration

mod_proxy directives like ProxyIOBufferSize could be used to configure mod_cluster.

There is no need to use ProxyPass directives because mod_cluster automatically configures which URLs have to be forwarded to JBossWEB.