Httpd mod proxy Configuration: Difference between revisions
Jump to navigation
Jump to search
| (4 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]] | ||
=Directives= | =Directives= | ||
| Line 27: | Line 21: | ||
* [[httpd ProxyPassInherit|ProxyPassInherit]] | * [[httpd ProxyPassInherit|ProxyPassInherit]] | ||
* [[httpd ProxyPassInterpolateEnv|ProxyPassInterpolateEnv]] | * [[httpd ProxyPassInterpolateEnv|ProxyPassInterpolateEnv]] | ||
* [[httpd | * [[httpd ProxyRequests|ProxyRequests]] | ||
* [[httpd ProxySet|ProxySet]] | * [[httpd ProxySet|ProxySet]] | ||
* [[httpd BalancerGrowth|BalancerGrowth]] | * [[httpd BalancerGrowth|BalancerGrowth]] | ||
| 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= | ||
A forward proxy is activated using the ProxyRequests directive. | A forward proxy is activated using the [[httpd ProxyRequests|ProxyRequests]] directive. | ||
=Reverse Proxy Configuration= | =Reverse 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
- Apache Module mod_proxy https://httpd.apache.org/docs/current/mod/mod_proxy.html
- Apache fails to proxy saying "No protocol handler was valid for the URL" https://access.redhat.com/solutions/277193
Internal
Directives
- ProxyPass
- Proxy
- ProxyTimeout
- ProxyPassReverse
- ProxyPassReverseCookieDomain
- ProxyPassReverseCookiePath
- ProxyPassMatch
- ProxyPassInherit
- ProxyPassInterpolateEnv
- ProxyRequests
- ProxySet
- BalancerGrowth
- BalancerInherit
- BalancerMember
- BalancerPersist
- ProxyAddHeaders
- ProxyBadHeader
- ProxyBlock
- ProxyDomain
- ProxyErrorOverride
- ProxyIOBufferSize
- ProxyReceiveBufferSize
- ProxyMatch
- ProxyMaxForwards
- ProxyStatus
- NoProxy
- ProxyRemote
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