describes more accurately what it does. For async MPMs, like EVENT, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported. • The DEFAULTTYPE directive HEARTMONITOR, MOD LBMETHOD HEARTBEAT Allow MOD PROXY BALANCER to base loadbalancing decisions on the number of active connections on the backend servers. MOD PROXY HTML Formerly a third-party module, this PROXY The PROXYPASS directive is now most optimally configured within a LOCATION or LOCATIONMATCH block, and offers a significant performance advantage over the traditional two-parameter syntax when present

describes more accurately what it does. For async MPMs, like EVENT, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported. • The DEFAULTTYPE directive HEARTMONITOR, MOD LBMETHOD HEARTBEAT Allow MOD PROXY BALANCER to base loadbalancing decisions on the number of active connections on the backend servers. MOD PROXY HTML Formerly a third-party module, this PROXY The PROXYPASS directive is now most optimally configured within a LOCATION or LOCATIONMATCH block, and offers a significant performance advantage over the traditional two-parameter syntax when present

describes more accurately what it does. For async MPMs, like EVENT, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported. • The DEFAULTTYPE directive HEARTMONITOR, MOD LBMETHOD HEARTBEAT Allow MOD PROXY BALANCER to base loadbalancing decisions on the number of active connections on the backend servers. MOD PROXY HTML Formerly a third-party module, this PROXY The PROXYPASS directive is now most optimally configured within a LOCATION or LOCATIONMATCH block, and offers a significant performance advantage over the traditional two-parameter syntax when present

describes more accurately what it does. For async MPMs, like EVENT, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported. • The DEFAULTTYPE directive HEARTMONITOR, MOD LBMETHOD HEARTBEAT Allow MOD PROXY BALANCER to base loadbalancing decisions on the number of active connections on the backend servers. MOD PROXY HTML Formerly a third-party module, this PROXY The PROXYPASS directive is now most optimally configured within a LOCATION or LOCATIONMATCH block, and offers a significant performance advantage over the traditional two-parameter syntax when present

describes more accurately what it does. For async MPMs, like event, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported. The DefaultType directive mod_heartmonitor, mod_lbmethod_heartbeat Allow mod_proxy_balancer to base loadbalancing decisions on the number of active connections on the backend servers. mod_proxy_html Formerly a third-party module, this mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch block, and offers a significant performance advantage over the traditional two-parameter syntax when present

describes more accurately what it does. For async MPMs, like event, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported. The DefaultType directive mod_heartmonitor, mod_lbmethod_heartbeat Allow mod_proxy_balancer to base loadbalancing decisions on the number of active connections on the backend servers. mod_proxy_html Formerly a third-party module, this mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch block, and offers a significant performance advantage over the traditional two-parameter syntax when present

describes more accurately what it does. For async MPMs, like event, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported. The DefaultType directive mod_heartmonitor, mod_lbmethod_heartbeat Allow mod_proxy_balancer to base loadbalancing decisions on the number of active connections on the backend servers. mod_proxy_html Formerly a third-party module, this mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch block, and offers a significant performance advantage over the traditional two-parameter syntax when present

describes more accurately what it does. For async MPMs, like event, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported. The DefaultType directive mod_heartmonitor, mod_lbmethod_heartbeat Allow mod_proxy_balancer to base loadbalancing decisions on the number of active connections on the backend servers. mod_proxy_html Formerly a third-party module, this mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch block, and offers a significant performance advantage over the traditional two-parameter syntax when present

describes more accurately what it does. For async MPMs, like event, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported. The DefaultType directive mod_heartmonitor, mod_lbmethod_heartbeat Allow mod_proxy_balancer to base loadbalancing decisions on the number of active connections on the backend servers. mod_proxy_html Formerly a third-party module, this mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch block, and offers a significant performance advantage over the traditional two-parameter syntax when present

describes more accurately what it does. For async MPMs, like event, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported. The DefaultType directive mod_heartmonitor, mod_lbmethod_heartbeat Allow mod_proxy_balancer to base loadbalancing decisions on the number of active connections on the backend servers. mod_proxy_html Formerly a third-party module, this mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch block, and offers a significant performance advantage over the traditional two-parameter syntax when present