Re: CGI, semicolons, and so on...

• Mail folder: WWW Talk Oct 93-present
• Next message: Joe Germuska: "Re: ismap functionality... "
• Previous message: Tony Sanders: "Re: ismap functionality... "
• In-reply-to: Robert S. Thau: "Re: CGI, semicolons, and so on..."

Message-id: <9312302118.AA28436@void.ncsa.uiuc.edu>
From: robm@ncsa.uiuc.edu (Rob McCool)
Date: Thu, 30 Dec 1993 15:18:12 -0600
In-Reply-To: rst@ai.mit.edu (Robert S. Thau)
       "Re: CGI, semicolons, and so on..." (Dec 30,  2:56pm)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: rst@ai.mit.edu (Robert S. Thau)
Subject: Re: CGI, semicolons, and so on...
Cc: www-talk@nxoc01.cern.ch
Content-Length: 1098

/*
 * Re: CGI, semicolons, and so on...  by Robert S. Thau (rst@ai.mit.edu)
 *    written on Dec 30,  2:56pm.
 *
 * Finally, in regards to 'nph' --- here's a somewhat wooly suggestion: Add
 * another possible keyword to the keys that the server recognizes when
 * parsing script output, along with "Content-type:" and "Location:" ---
 * something like 'Verbatim:'.  Then mandate that if the first characters of
 * the script's output are "Verbatim:\n", the rest of it will be passed to the
 * client unaltered.  As far as I can tell, this is backward compatible.  How
 * about it?
 * 
 */

Was brought up in the original nph- discussions... in fact the spec had
something like that for a week or two. The problem is, the entire reason for
nph- is to allow the script direct access to the client without *any* server
intervention... in other words, the server has to know that a script is
going to put out its own header before execution... therefore, the question
was either to make a naming convention or have the server authors add
configuration options. The former was eventually chosen.

--Rob