W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1997

Re: Common Gateway Interface

From: Dylan Barrell <dbarrell@hotmail.com>
Date: Fri, 30 May 1997 00:38:28 PDT
Message-Id: <199705300738.AAA21384@f47.hotmail.com>
To: hallam@ai.mit.edu, dbarrell@hotmail.com
Cc: http-wg@cuckoo.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/3369
I didn't say that we should necessarily standardise the CGI implementation but 
we should specify which header fields MAY be passed, which MUST be passed and 
which MAY NOT be passed to CGI, NSAPI, ISAPI or JOHNDOESAPI. I also beleive 
every RFC concerning HTTP or an extension to it which adds to the headers should 
deal with this issue.

Failure to do this will force each Internet, Intranet and Extranet developer to 
write his own HTTP daemon in order to be assured of having access to all the 
information she needs. I would prefer them to be able to use standard HTTP 
daemons and (regardless of the API, or inteface which they use to integrate with 
it) can write applications and be assured which data they have access to.

If we beleive that standards are a good thing (and I certainly hope we do) then 
we should also believe in standards which will standardise the interoperability 
of HTTP daemons and applications. It will benefit the industry.

Ultimately I would like to see the interface between daemons and applications 
standardised and (even though you don't consider the API to be a good one) there 
is one precedence for an API within the IETF - GSS-API.


From hallam@life.ai.mit.edu Thu May 29 14:29:44 1997
>Received: from muesli.ai.mit.edu (muesli.ai.mit.edu [])
>	by life.ai.mit.edu (8.8.5/AI1.15/ai.master.life:1.15) with ESMTP id RAA19528;
>	Thu, 29 May 1997 17:26:40 -0400 (EDT)
>From: Hallam-Baker <hallam@ai.mit.edu>
>Received: (from hallam@localhost)
>	by muesli.ai.mit.edu (8.8.5/8.8.5AI/ai.client:1.5) id RAA25737;
>	Thu, 29 May 1997 17:24:22 -0400 (EDT)
>Message-Id: <199705292124.RAA25737@muesli.ai.mit.edu>
>Subject: Re: Common Gateway Interface
>To: dbarrell@hotmail.com (Dylan Barrell)
>Date: Thu, 29 May 1997 17:24:19 -0400 (EDT)
>Cc: http-wg@cuckoo.hpl.hp.com
>In-Reply-To: <199705292039.NAA22475@f22.hotmail.com> from "Dylan Barrell" at 
May 29, 97 01:39:35 pm
>X-Mailer: ELM [version 2.4 PL25]
>MIME-Version: 1.0
>Content-Type: text/plain; charset=US-ASCII
>Content-Transfer-Encoding: 7bit
>> Why is there absolutely no mention of the CGI interaction between the HTTP 
>> daemon and the CGI programs? Surely this standard should specify which 
peices> the header are made available to CGI programs and how they are made 
>Because CGI is not an IETF spec, it was a hack put together by Ari
>Luotenen of CERN and Rob McCool at NCSA to allow people to plug
>stuff into both their servers. While their Netscape server supports
>CGI the prefered way to plug in a module is via NSAPI which is 
>much more efficient because it does not spawn a process for each
>CGI is completely inappropriate to standardize in the IETF. It is
>operating system specific and its an API and not a protocol. The
>W3C might have an interest in producing a spec but I would not
>count on it. It might be nice to have a document readily available 
>with Ari and Rob's names on it but it really isn't a technology
>that should be considered leading edge at this point. NSAPI and 
>ISAPI have replaced it, there are many, many such APIs and there
>is no particular reason to consider CGI as a special case even
>if popular Web books have "CGI" on the cover in letters three 
>inch high.
>		Phill

Get Your *Web-Based* Free Email at http://www.hotmail.com
Received on Friday, 30 May 1997 00:43:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:20 UTC