Httpd mod proxy Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
=External= | =External= | ||
* https://httpd.apache.org/docs/current/mod/mod_proxy.html | * 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 | * Apache fails to proxy saying "No protocol handler was valid for the URL" https://access.redhat.com/solutions/277193 | ||
Revision as of 19:24, 22 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
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>