RFC 3875 on The Common Gateway Interface (CGI) Version 1.1

rfc-editor@rfc-editor.org Wed, 27 October 2004 00:33 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13851; Tue, 26 Oct 2004 20:33:22 -0400 (EDT)
Received: from megatron.ietf.org ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMbyT-0007Tp-71; Tue, 26 Oct 2004 20:47:37 -0400
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMbWZ-0000nC-9n; Tue, 26 Oct 2004 20:18:47 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMZpr-0004WV-Lo for ietf-announce@megatron.ietf.org; Tue, 26 Oct 2004 18:30:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11895 for <ietf-announce@ietf.org>; Tue, 26 Oct 2004 18:30:32 -0400 (EDT)
Received: from boreas.isi.edu ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMa3Y-0005L5-6d for ietf-announce@ietf.org; Tue, 26 Oct 2004 18:44:47 -0400
Received: from ISI.EDU (adma.isi.edu []) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i9QMTni07828; Tue, 26 Oct 2004 15:29:49 -0700 (PDT)
Message-Id: <200410262229.i9QMTni07828@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 26 Oct 2004 15:29:49 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: rfc-editor@rfc-editor.org
Subject: RFC 3875 on The Common Gateway Interface (CGI) Version 1.1
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f

A new Request for Comments is now available in online RFC libraries.

        RFC 3975

        Title:      The Common Gateway Interface (CGI) Version 1.1
        Author(s):  D. Robinson, K. Coar
        Status:     Informational
        Date:       October 2004
        Mailbox:    drtr@apache.org, coar@apache.org
        Pages:      36
        Characters: 80728
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-coar-cgi-v11-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3875.txt

The Common Gateway Interface (CGI) is a simple interface for running
external programs, software or gateways under an information server
in a platform-independent manner.  Currently, the supported
information servers are HTTP servers.

The interface has been in use by the World-Wide Web (WWW) since 1993.
This specification defines the 'current practice' parameters of the
'CGI/1.1' interface developed and documented at the U.S. National
Centre for Supercomputing Applications.  This document also defines
the use of the CGI/1.1 interface on UNIX(R) and other, similar

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
IETF-Announce mailing list