Project

General

Profile

Actions

Bug #1053

closed

Loading mod_cgi before mod_fastcgi breaks running CGIs

Added by Anonymous about 18 years ago. Updated over 16 years ago.

Status:
Invalid
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

When one loads mod_cgi before mod_fastcgi, all CGI responses are empty. The CGI gets fully executed, however, and a SIGPIPE is sent to it. But the HTTP response is empty.

Valid configuration:


config {
    var.PID              = 16406
    server.modules       = ("mod_indexfile", "mod_fastcgi", "mod_cgi", "mod_dirlisting", "mod_staticfile")
    server.document-root = "." 
    server.errorlog      = "lighttpd.errors" 
    server.port          = 9203
    server.event-handler = "freebsd-kqueue" 
    cgi.assign           = (
        "/test" => "/usr/local/bin/ruby",
    )
    fastcgi.server       = (
        "test.fcgi" => (
            "localhost" => (
                "min-procs" => 1,
                "socket"    => "/tmp/rack-test-fcgi",
                "bin-path"  => "test.fcgi",
                # 3
            ),
        ),
    )

}

Broken configuration:


config {
    var.PID              = 16421
    server.modules       = ("mod_indexfile", "mod_cgi", "mod_fastcgi", "mod_dirlisting", "mod_staticfile")
    server.document-root = "." 
    server.errorlog      = "lighttpd.errors" 
    server.port          = 9203
    server.event-handler = "freebsd-kqueue" 
    cgi.assign           = (
        "/test" => "/usr/local/bin/ruby",
    )
    fastcgi.server       = (
        "test.fcgi" => (
            "localhost" => (
                "min-procs" => 1,
                "socket"    => "/tmp/rack-test-fcgi",
                "bin-path"  => "test.fcgi",
                # 3
            ),
        ),
    )

}

As you can see, the only difference is the load order.

The FCGI works in both cases.

-- chneukirchen

Actions #1

Updated by darix about 18 years ago

can you please see if 1.4.13 fixes the bug for you?

Actions #2

Updated by darix about 18 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

reporter just verified that 1.4.13 doesnt show this bug anymore.

Actions #3

Updated by stbuehler over 16 years ago

  • Status changed from Fixed to Invalid
Actions

Also available in: Atom