Actions
Feature #2372
closedmod_*cgi and ipv6 address
ASK QUESTIONS IN Forums:
Description
i'm seeing unexpected behaviour with using mod_scgi and binding to the ipv6 loopback address.
my scgi listener on ::1 port 6500 does not receive a connection when trying to access the document root.
without using ipv6 for the server and listening\binding instead on 127.0.0.1 it works. see following error messages, which appear when trying to access the first time.
lines from the error.log
2011-12-09 21:54:36: (mod_scgi.c.1349) converting IP-adress failed for 0:0:0:0:0:0:0:1 Be sure to specify an IP address here 2011-12-09 21:54:36: (mod_scgi.c.2389) fcgi-server disabled: 0:0:0:0:0:0:0:1 6500 2011-12-09 22:26:54: (mod_scgi.c.2065) proc: ::1 6500 5 0 0 0 2011-12-09 22:26:54: (mod_scgi.c.2769) all handlers for / on / are down.
lines from lighttpd.conf
server.use-ipv6 = "enable" server.bind = "0:0:0:0:0:0:0:1" scgi.server = ("/" => (("host" => server.bind, "port" => 6500, "check-local" => "disable")))
system info
lighttpd/1.4.29 on linux 3.1.4
i also tried using "::1" and "0::1" as address with the same result.
Updated by darix almost 13 years ago
I dont think IPv6 is supported for FastCGI/SCGI backends
Updated by stbuehler over 12 years ago
- Tracker changed from Bug to Feature
- Subject changed from mod_scgi and ipv6 address to mod_*cgi and ipv6 address
- Target version set to 1.4.x
I don't think we'll add this in 1.4.x, but just for reference...
Updated by gstrauss over 8 years ago
- Related to Feature #1537: mod_proxy + ipv6 added
Updated by gstrauss over 8 years ago
- Status changed from New to Patch Pending
- Target version changed from 1.4.x to 1.4.40
Updated by gstrauss over 8 years ago
- Status changed from Patch Pending to Fixed
- % Done changed from 0 to 100
Applied in changeset 4059dcd60e30cc81763e5a8690abeccbb43fca2d.
Actions
Also available in: Atom