Httpd mod proxy Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 46: | Line 46: | ||
=mod_proxy mod_cluster Configuration= | =mod_proxy mod_cluster Configuration= | ||
mod_proxy directives like ProxyIOBufferSize could be used to configure mod_cluster. | mod_proxy directives like [[httpd ProxyIOBufferSize|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. | There is no need to use ProxyPass directives because mod_cluster automatically configures which URLs have to be forwarded to JBossWEB. | ||
Revision as of 02:59, 23 December 2016
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
Secure mod_proxy
TODO
Directives
- ProxyPass
- ProxyIOBufferSize
- ProxyTimeout
- ProxyPassReverse
- ProxyPassReverseCookieDomain
- ProxyPassReverseCookiePath
- ProxyRequest
- ProxySet
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.