Httpd Proxy: Difference between revisions
Jump to navigation
Jump to search
| (5 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
=Internal= | =Internal= | ||
* [[Httpd mod_proxy Configuration#Directives|mod_proxy Configuration]] | |||
* [[Httpd_mod_proxy_Concepts#.3CProxy.3E_Control_Block|mod_proxy Concepts - <Proxy> Control Block]] | * [[Httpd_mod_proxy_Concepts#.3CProxy.3E_Control_Block|mod_proxy Concepts - <Proxy> Control Block]] | ||
=Overview= | =Overview= | ||
| Line 32: | Line 32: | ||
</blockquote> | </blockquote> | ||
= | =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 style="background-color: | |||
:[[ | |||
</blockquote> | </blockquote> | ||
Latest revision as of 19:58, 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.