Bug #516
using round-robin as a balance scheme to reverse proxy to a single server doesn't seem to work
| Status: | Fixed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | mod_proxy | |||
| Target version: | - | |||
| Missing in 1.5.x: |
Description
Hi, I'm using lighttpd 1.4.10 on a CentOS 4.2/x86-64 box which has
been configured to be a reverse proxy to Apache 2.2/mod-php server.
lighttpd listens on the routable IP port 80 and Apache listens on
127.0.0.1 port 80
If I have the following config
$SERVER["socket"] == "ip.ad.dr.ess:80" {
proxy.balance = "round-robin"
proxy.server = ( "" => ( ( "host" => "127.0.0.1" )
) )
}
I get the following when I visit the website hosted on the ip
2006-02-11 04:23:14: (log.c.75) server started 2006-02-11 04:23:22: (mod_proxy.c.1249) no proxy-handler found for: / 2006-02-11 04:23:22: (mod_proxy.c.1249) no proxy-handler found for: /favicon.ico
switching proxy.balance to either "hash" or "fair" makes everything
work. Does anybody else use "round-robin" as a reverse proxy balance
mechanism. I was hoping round-robin would become a no-op when there
is only one backend server.
-- yusufg
History
#1 Updated by Anonymous over 6 years ago
$SERVERsocket == "ip.ad.dr.ess:80" {
proxy.balance = "round-robin"
proxy.server = ( "" => ( ( "host" => "127.0.0.1" )
) )
#2 Updated by Anonymous about 6 years ago
I'm seeing the same problem with 1.4.15. Is anybody reading these bug reports?
#3 Updated by stbuehler over 5 years ago
I think i found the bug, patch attached.
#4 Updated by stbuehler about 5 years ago
- Status changed from New to Fixed
- Resolution set to fixed
Fixed in r2092
Also available in: Atom
