- From: Carlos A. Varela <cvarela@isr.co.jp>
- Date: Fri, 30 May 1997 08:51:48 +0900
- To: Dylan Barrell <dbarrell@hotmail.com>
- Cc: http-wg@cuckoo.hpl.hp.com
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: http://hoohoo.ncsa.uiuc.edu/cgi/env.html reads: ------------------------------------------------------------------ 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. HTTP_ACCEPT 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 HTTP_USER_AGENT 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