httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 53388] mod_proxy_balanser generates 503 when proxying to a balancermember which isn't defined
Date Tue, 12 Jun 2012 09:38:22 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=53388

--- Comment #1 from Eric Garreau <egarreau@gmail.com> ---
Hi

use <Proxy balancer://idm> and it should work better ;-)

from my personal experience, my advice is to use the <Proxy> object as a pure
substitution for {protocol://host:port}, and nothing more.

<Proxy balancer://foo>
    # do not add a trailing '/' after IP:PORT  (do not add a path, too)
    BalancerMember       http://127.0.0.1:1234
    BalancerMember       http://127.0.0.1:2345
</Proxy>

this view allows to clarify the substitution which is made by
mod_proxy_balancer, by keeping equivalent things together:
 - level: substitute protocol://host:port (balancer's job)
    * balancer://foo  --->  http://127.0.0.1:1234
 - level: substitute request path  (ProxyPass' job)
    * balancer://foo/path1  -->  http://127.0.0.1:1234/path2

I found this logic to be a safe method to avoid the famous "double /"
side-effect that you get when you want to "ProxyPass /"...

eric

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message