Project

General

Profile

Feature #2372

mod_*cgi and ipv6 address

Added by tantalum over 5 years ago. Updated 11 months ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
mod_scgi
Target version:
Start date:
2011-12-09
Due date:
% Done:

100%

Missing in 1.5.x:
No

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.


Related issues

Related to Feature #1537: mod_proxy + ipv6 Fixed

Associated revisions

Revision 4059dcd6 (diff)
Added by gstrauss 11 months ago

[mod_fastcgi,mod_scgi] IPv6 support (fixes #2372)

(similar to mod_proxy issue https://redmine.lighttpd.net/issues/1537)

x-ref:
"mod_*cgi and ipv6 address"
https://redmine.lighttpd.net/issues/2372
"mod_proxy + ipv6"
https://redmine.lighttpd.net/issues/1537

github: closes #60

History

#1 Updated by darix over 5 years ago

I dont think IPv6 is supported for FastCGI/SCGI backends

#2 Updated by stbuehler almost 5 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...

#3 Updated by gstrauss 11 months ago

#4 Updated by gstrauss 11 months ago

  • Status changed from New to Patch Pending
  • Target version changed from 1.4.x to 1.4.40

#5 Updated by gstrauss 11 months ago

  • Status changed from Patch Pending to Fixed
  • % Done changed from 0 to 100

Also available in: Atom