[CGI Project]

Common Gateway Interface
RFC Project Page


Last updated
This document uses HTML 4.0 and CSS2 Style Sheets.
The concept for the CGI logo was taken from the original used by the NCSA CGI project.


This is the repository for the effort (reactivated in November of 1997) to turn the de facto Common Gateway Interface "standard" into an actual Informational RFC. The current effort has been based upon a draft composed by David Robinson, and much of his work has survived. That draft expired in July of 1997, however.

If you are a CGI script writer, please consider rating the usefulness of the information on these pages at the CGI Resource Index. Thanks!

Document List

Even though the official format of RFCs and Internet Drafts is plain text formatted for A-size paper, the working documents here are primarily written in HTML for convenience and ease of markup. As a result, please include a document name, section number, and some context when remarking on the text - page numbers aren't useful.

Special note: The HTML documents in this repository are written compliant to the HTML 4.0 recommendation, and use CSS2 style sheets. If your browser cannot handle these features, please upgrade to one that can. If you can't, please let the working-group chair know. (You can tell if your browser can handle these features by whether the first line of each of the following bullet items is red; if they are, it does.)

The CGI/1.1 Specification

Goal: Clearly and concisely codify "current practice" of CGI/1.1 usage on the Web as of 1999.

  • CGI/1.1 Revision 03 (HTML, HTML [showing changes from draft 02 in fuchsia], plaintext),
    [ACTIVE Internet-Draft expiring on 31 December 1999]
    Third revision of the CGI/1.1 draft, potentially our candidate for RFC submission. Lots of security considerations added, BNF production corrections, and disambiguated ambiguities; see the document for details.
  • Current list of issues with the CGI/1.1 draft (HTML),
    A frameset document listing the issues that have been raised to date with the CGI/1.1 working draft
    If your browser is not frames-capable, the issues list can be found here.
  • CGI/1.1 Revision 02 (HTML, HTML [showing changes from draft 01 in red], plaintext),
    [SUPERSEDED Internet-Draft expiring on 14 October 1999]
    Second revision of the CGI/1.1 draft, addressing changes for typos, combination of Location and Status response header fields, and server processing of request content-bodies. Also included new Internet-Draft language.
  • CGI/1.1 Revision 01 (HTML, HTML [showing changes from draft 00 in green], plaintext),
    [SUPERSEDED Internet-Draft expiring on 8 May 1999]
    First revision of draft revision 00, incorporating suggestions, edits, and corrections made through the mailing list.
  • CGI/1.1 Revision 00 (HTML, plaintext),
    [EXPIRED Internet-Draft expiring on 29 November 1998]
    First draft attempting to formally describing CGI/1.1 "current practice" in Internet-Draft/RFC format.
  • The CGI/1.2 ("Next Generation") Specification

    Goal: To address problems and deficiencies of CGI as it is currently deployed.

  • Current CGI/1.2 working document (HTML),
    [Not yet published Internet Draft]
    Originally based upon the RFCED draft; right now this document is not up-to-date, since it will be based upon the final CGI/1.1 RFC if-and-when -- and that hasn't been completed yet.
  • Current list of issues with the CGI/1.2 draft (HTML),
    A frameset document listing the issues that have been raised to date with the CGI/1.2 working draft
    If your browser is not frames-capable, the issues list can be found here.
  • Please don't bookmark the individual documents, as the names are changed periodically and your links will go stale.

    Summary

    The original thrust of this latest effort was to formulate an enhanced CGI specification, called CGI/1.2, which was a proper superset of the CGI/1.1 functionality. This turned out to be the cause of some confusion, so the plan was changed.

    To confuse matters further, the draft was mistakenly submitted to the RFC Editor rather than the Internet Drafts Editor. This has been corrected.

    The new plan is as follows:

    1. Edit the Revision 00 RFCED draft to remove the CGI/1.2-isms
      (Done)
    2. Submit the edited document to the Internet Drafts editor so it can be reviewed and adjusted to reflect current practice
      (Draft 00: Done; Draft 01: Done; Draft 02: in the works)
    3. When it's ready, submit for processing as an Informational RFC describing CGI/1.1
    4. With the CGI/1.1 RFC submission as a basis, develop an Internet Draft describing CGI/1.2
    5. Identify additional problems and shortcomings in the CGI/1.1 specification and CGI/1.2 draft and address them in subsequent CGI/1.2 draft revisions
    6. Submit the final CGI/1.2 draft for consideration as an Experimental RFC describing the "next generation" of CGI, CGI/1.2.

    Schedule

    How far is up? Seriously, more issues are being identified all the time, so there's no clear indication when the CGI/1.2 work will be ready for RFC submission. The rework of the original RFCED Revision 00 document into an Internet Draft describing CGI/1.1 current practice is complete and the I-D revision 00 submission was made at the end of May, 1998. The 01 revision of the CGI/1.1 draft has also been completed and submitted for to the Internet Drafts editor for release. It was first submitted in late November, after the blackout period preceding the IETF meeting, so it was re-submitted on 8 December 1998 (including a couple of additional changes). It's even possible that the 01 draft can be submitted for acceptance as an Informational RFC.

    That's the plan, anyway. :-)

    How to Participate

    The mailing list for discussing this draft can be found at CGI-WG@Golux.Com, and it is open to all. Submissions can only be made by subscribed members (an anti-spam measure). In other words, don't send mail to that address unless you've joined the list! To subscribe to the list, which is managed by Majordomo, send a message to CGI-WG-Request@Golux.Com with the word "subscribe" in the body (not the subject!) of the message.

    Being on the list is the only way you can see the discussions and make your own comments. The list archives are now available for general consumption via the Web at <URL:http://Web.Golux.Com/coar/cgi/archives/> Once you're on the mailing list you can also access them through email.

    If you have questions, please contact the chair of the "working group," Ken Coar.