[6027] in www-talk@info.cern.ch

home help back first fref pref prev next nref lref last post

extend CGI

daemon@ATHENA.MIT.EDU (Rick Troth)
Tue Oct 4 08:08:27 1994

Date: Tue, 4 Oct 1994 13:04:20 +0100
Errors-To: listmaster@www0.cern.ch
Errors-To: listmaster@www0.cern.ch
Reply-To: TROTH@UA1VM.UA.EDU
From: Rick Troth <TROTH@UA1VM.UA.EDU>
To: Multiple recipients of list <www-talk@www0.cern.ch>

        I find the need for another variable in the CGI spec.
Maybe I'm misunderstanding what's already there.   Maybe someone could
help me?   Maybe CGI really needs to be improved.   What do y'all think?

        I don't see a variable for that  "extra info"  that comes
after the script name in some cases.   For example,  imagemap has to
have some reference to which map to use.   Now I've argued that we
should use something other than a slash to delimit the "extra" from
the path to imagemap,  but it doesn't matter.   As long as the server
knows what to do,  it can isolate the "extra" and stash it in an
environment variable.   So ... what do we call that variable?

        I'm thinking  PATH_EXTRA.   This is to compliment  PATH_INFO,
PATH_TRANSLATED,  and  SCRIPT_NAME,  none of which  (I think)  do what
I'm looking for.   I suppose we could have the scripts parse  PATH_INFO,
but isn't this something that the server should do?

--
Rick Troth, <rmtroth@aol.com>, <troth@ua1vm.ua.edu>, Houston, Texas, USA

home help back first fref pref prev next nref lref last post