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

Re: Common Gateway Interface

From: Carlos A. Varela <cvarela@isr.co.jp>
Date: Fri, 30 May 1997 08:51:48 +0900
Message-Id: <199705292351.IAA03386@enrique.isr.co.jp>
To: Dylan Barrell <dbarrell@hotmail.com>
Cc: http-wg@cuckoo.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/3366
On May 29, 13:39, "Dylan Barrell" wrote:
| --- Subject: Common Gateway Interface
| 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 of 
| the header are made available to CGI programs and how they are made available

Read the CGI specification.   In particular:




In addition to these, the header lines received from the client, if
any, are placed into the environment with the prefix HTTP_ followed
by the header name. Any - characters in the header name are changed
to _ characters. The server may exclude any headers which it has
already processed, such as Authorization, Content-type, and
Content-length. If necessary, the server may choose to exclude any
or all of these headers if including them would exceed any system
environment limits. 

An example of this is the HTTP_ACCEPT variable which was defined in
CGI/1.0. Another example is the header User-Agent.


     The MIME types which the client will accept, as given by HTTP
     headers. Other protocols may need to get this information from
     elsewhere. Each item in this list should be separated by commas
     as per the HTTP spec. 

     Format: type/subtype, type/subtype 


     The browser the client is using to send the request. General
     format: software/version library/version.

- Carlos A. Varela
  cvarela@ncsa.uiuc.edu, cvarela@isr.co.jp
Received on Thursday, 29 May 1997 16:55:04 UTC

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