Httpd mod proxy Configuration

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

• mod_proxy
• mod_cluster Configuration

Secure mod_proxy

TODO

Directives

• ProxyPass

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.

Reference

ProxyIOBufferSize

The ProxyIOBufferSize directive adjusts the size of the internal buffer which is used as a scratchpad for the data between input and output. The default value is 8192 bytes.

If used with AJP, this directive sets the maximum AJP packet size in bytes. Values larger than 65536 are set to 65536.

If the value is changed from the default, the AJP connector packetSize must be also changed on the Tomcat side.

ProxyTimeout

This directive allows a user to specifiy a timeout on proxy requests. This is useful when the application server is slow, and you would rather just return a timeout and fail gracefully instead of waiting however long it takes the server to return.