CGI command-line parameters

Chris Adie <CJA@ml0.ucs.edinburgh.ac.uk>

Mail folder: WWW Talk Apr 94-present
Next message: Brandon Plewe: "Browser/Server Evaluation Project"
Previous message: neuss@igd.fhg.de: "Re: Web Document Retrieval"

Errors-To: listmaster@www0.cern.ch
Date: Mon, 16 May 1994 19:20:17 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <2A658F06136@ml0.ucs.ed.ac.uk>
Errors-To: listmaster@www0.cern.ch
Reply-To: CJA@ml0.ucs.edinburgh.ac.uk
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Chris Adie <CJA@ml0.ucs.edinburgh.ac.uk>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: CGI command-line parameters
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Mailer: Pegasus Mail v3.1 (R1a)
X-Mailer: Pegasus Mail v3.1 (R1a)
Priority: normal
Priority: normal
Organization: Computing Service
Organization: Computing Service

The CGI spec says that if a query string does not contain an = character,
then the server passes it as a command-line parameter to the script (as
well as providing it in the QUERY_STRING environment variable).

The QUERY_STRING environment variable contains the undecoded query
information (ie %xx is not interpreted).

Should the query string be decoded before being passed to the script on
the command line?

(I would argue that it should be decoded.)

Second question - what is the difference between CGI/1.0 and CGI/1.1?


Regards,

Chris Adie                                   Phone:  +44 31 650 3363
Edinburgh University Computing Service       Fax:    +44 31 662 4809
University Library, George Square            Email:  C.J.Adie@edinburgh.ac.uk
Edinburgh EH8 9LJ, United Kingdom