Httpd mod proxy Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 9: Line 9:
* [[Mod_cluster Configuration|mod_cluster Configuration]]
* [[Mod_cluster Configuration|mod_cluster Configuration]]
* [[httpd Configuration]]
* [[httpd Configuration]]
=Secure mod_proxy=
<font color=red>
TODO
</font>


=Directives=
=Directives=
Line 42: Line 36:
* [[httpd ProxyMatch|ProxyMatch]]
* [[httpd ProxyMatch|ProxyMatch]]
* ProxyMaxForwards
* ProxyMaxForwards
* [[httpd ProxyStatus|ProxyStatus]]
* [[httpd NoProxy|NoProxy]]
* [[httpd ProxyRemote|ProxyRemote]]


=Forward Proxy Configuration=
=Forward Proxy Configuration=
Line 66: Line 63:


There is no need to use ProxyPass directives because mod_cluster automatically configures which URLs have to be forwarded to JBossWEB.
There is no need to use ProxyPass directives because mod_cluster automatically configures which URLs have to be forwarded to JBossWEB.
=Secure mod_proxy=
<font color=red>
TODO
</font>

Latest revision as of 17:00, 10 January 2017

External

Internal

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.

Secure mod_proxy

TODO