Project

General

Profile

Actions
Copy link

Bug #429

closed

lighttpd-1.4.8 mod_cgi: no variables with GET?

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

Status:
Wontfix
Priority:
Normal
Category:
mod_cgi
Target version:
-
ASK QUESTIONS IN Forums:

Description

Problem: When I search my database with a POST call to mod_cgi
I get back a list of links that look like this:

<p>4 <a href="ifetch?2000+531120375329+F">Japan: Government plans
         law revision to prevent espionage</a><br>
Calling the shell script "ifetch" with 3 variables:
ifetch?2000+531120375329+F
Apache: http://localhost:8000/cgi-bin/ifetch?2000+531120375329+F
returns:
ifetch /var/www/db 2000 531120375329 F
        3 args
lighttpd: http://localhost/cgi-bin/ifetch?2000+531120375329+F
returns:
/usr/lib/cgi-bin/ifetch /var/www/db
        0 args
parrot.pl tells that that the browser is sending:
GET /cgi-bin/ifetch?2000+473418041343+F HTTP/1.1
        Host: localhost:8080
        :
        : (omitted)
In the script below, you will see that "ifetch" just calls
    another program and passes the variables.
The goal is to return the record with the key=531120375329
    from the database.
Apache does it. lighttpd doesn't, because no variables
    are passed.

My machine:

Linux magadan 2.6.8-2-386 #1 Tue Aug 16 12:46:35 UTC 2005 i686 GNU/Linux

The web servers:

lighttpd-1.4.8 built from source  (running on port 80)
    apache2_2.0.54-5_i386.deb    (running on port 8000)

Inclusions:

1. my cgi program "ifetch" (attached below)
2. lighttpd.conf  (attached below)

Configuration:

I don't think that this is a configuration problem, but I
    could be wrong.
Everything is just plain vanilla.
Any guidance greatly appreciated.

=========================================================================
"ifetch" {{{
#!/bin/sh

  1. From this script, run the isrch_fetch utility and pass 4 arguments:
  2. $1=dbname, $2=key, $3=field
  3. isrch_fetch <databases_path> $1 $2 $3 #
  1. ---- original -------
    #exec /usr/local/bin/isrch_fetch /var/www/db $1 $2 $3
  1. ----- my testing ----------
    echo "Content-type: text/plain"
    echo ""
    echo $0 /var/www/db $1 $2 $3
    echo "$# args"
    }}}

-- valliant

Actions
Copy link
 #1

Updated by Anonymous almost 17 years ago

i'm having a very similar problem with a simpler test case


#!/bin/sh

echo "content-type: text/plain" 
echo

echo $# $@

then http://localhost/cgi-bin/test?asdf

which outputs just 0

instead of 1 asdf

Actions
Copy link
 #2

Updated by stbuehler almost 17 years ago

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

If i read the spec correctly, we don't have to pass the query-string in the command line, we only should if it doesn't contain a unencoded '=', but we are allowed to not do that due to "internal limitations".

So i think you should just use the traditional way via $QUERY_STRING - it is easier for you (you have to accept it via $QUERY_STRING anyway if is too long) and easier for us.

Actions
Copy link
 #3

Updated by stbuehler over 16 years ago

  • Status changed from Fixed to Wontfix
Actions
Copy link
 #4

Updated by jlc about 16 years ago

I believe this is the wrong decision. There are a lot of CGI programs available that use the command line. It is a hassle to rewrite the ones needed just for lighttpd. As far as I am aware, lighttpd is the only popular server that does not support the CGI command line. Even thttpd supports it.

The "internal limitations" is referring to the operating system, specifically exec() or shell limitations. This has not been a problem for UNIX or Linux in years.

Actions
Copy link

Also available in: Atom