Httpd Proxy: Difference between revisions
| Line 33: | Line 33: | ||
=Load Balancing Configuration= | =Load Balancing Configuration= | ||
<blockquote style="background-color: Gold; border: solid thin Goldenrod;"> | |||
:<br>Load balancing configuration at <Proxy> level uses the same configuration elements as [[Httpd_ProxyPass#Load_Balancing_Configuration|ProxyPass load balancing configuration]].<br><br> | |||
</blockquote> | |||
==lbmethod== | ==lbmethod== | ||
Revision as of 00:57, 3 January 2017
External
Internal
Overview
Container directive for directives applied to proxied resources. Directives placed in <Proxy> sections apply only to matching proxied content.
Matching
A backend URL matches the configuration section of a <Proxy> container directive if it begins with the wildcard-url string, even if the last path segment in the directive only matches a prefix of the backend URL. For example <Proxy "http://example.com/a"> matches "http://example.com/a/b". This behavior differs from the behavior of <Location>.
Syntax
<Proxy wildcard-url> ... </Proxy>
<Proxy> and Balancer Workers
If the Proxy directive scheme starts with "balancer://", the directive defines the members of a virtual worker that balances amongst its members. For more details see:
Load Balancing Configuration
Load balancing configuration at <Proxy> level uses the same configuration elements as ProxyPass load balancing configuration.
lbmethod
Defines the load balancing scheduler method to use. Available options:
- byrequests
- bytraffic
- bybusyness
The default value is "byrequests".
The load balancing dynamics is explained here: Httpd_mod_proxy_Concepts#mod_proxy Concepts - Load_Balancing.
maxattempts
The maximum number of failover attempts before giving up. The default is equal with the number of members minus 1, or 1 if there is a single member. The load balancing dynamics is explained here: mod_proxy Concepts - Load_Balancing.