[1]
[CITE@ja[mod_proxy - Apache HTTP サーバ]] ([CODE[2007-09-02 22:53:05 +09:00]] 版) <http://httpd.apache.org/docs/2.2/ja/mod/mod_proxy.html#ProxyPass>

> Proxy ディレクティブのスキームが balancer:// になっている場合は、 バックエンドサーバと実際には通信しない仮想ワーカーが生成されます。 このワーカーは幾つかの "本物の" ワーカーの管理をつかさどります。 この場合パラメータは、この仮想ワーカーに対して設定されます。




[FIG(quote)[
[FIGCAPTION[
[2] [CITE@en[mod_proxy - Apache HTTP Server Version 2.4]]
([TIME[2015-02-15 17:51:02 +09:00]] 版)
<http://httpd.apache.org/docs/current/en/mod/mod_proxy.html>
]FIGCAPTION]

> A balancer worker is created if its worker URL uses balancer as the protocol scheme. The balancer URL uniquely identifies the balancer worker. Members are added to a balancer using BalancerMember.

]FIG]


[FIG(quote)[
[FIGCAPTION[
[3] [CITE@en[mod_proxy - Apache HTTP Server Version 2.4]]
([TIME[2015-02-15 17:51:02 +09:00]] 版)
<http://httpd.apache.org/docs/current/en/mod/mod_proxy.html#ProxyPass>
]FIGCAPTION]

> If the Proxy directive scheme starts with the balancer:// (eg: balancer://cluster, any path information is ignored) then a virtual worker that does not really communicate with the backend server will be created.

]FIG]


[FIG(quote)[
[FIGCAPTION[
[4] [CITE@en[mod_proxy_ajp - Apache HTTP Server Version 2.4]]
([TIME[2015-01-02 20:49:24 +09:00]] 版)
<http://httpd.apache.org/docs/current/en/mod/mod_proxy_ajp.html>
]FIGCAPTION]

> <Proxy balancer://cluster>
>     BalancerMember ajp://app1.example.com:8009 loadfactor=1
>     BalancerMember ajp://app2.example.com:8009 loadfactor=2
>     ProxySet lbmethod=bytraffic
> </Proxy>
> ProxyPass /app balancer://cluster/app

]FIG]


[5] [CITE@en[mod_proxy_balancer - Apache HTTP Server Version 2.4]], [TIME[2020-07-28T12:39:54.000Z]], [TIME[2020-10-01T02:03:35.602Z]] <https://httpd.apache.org/docs/current/en/mod/mod_proxy_balancer.html>