CGI手册RFC3875.pdf资源-CSDN文库

需积分: 10 173 浏览量 2021-07-22 09:45:11 上传评论收藏 115KB PDF 举报

《CGI手册RFC3875.pdf》是网络工作小组(D. Robinson)发布的一份信息性文档，由Apache软件基金会出版。RFC3875详细阐述了通用网关接口(Common Gateway Interface, CGI)版本1.1的相关知识。这份文档并不定义任何互联网标准，但为互联网社区提供了有价值的信息。其版权归属于互联网协会(2004)，并且不受限于任何形式的分布。 CGI是一种在平台无关性基础上，使得外部程序、软件或网关能在信息服务器（主要指HTTP服务器）上运行的简单接口。自1993年以来，它已被广泛应用于万维网(www)。此规范定义了“当前实践”参数，即在U.S. 国家超级计算应用中心开发和记录的“CGI/1.1”接口。同时，该文档还涵盖了在UNIX和其他类似系统上使用CGI/1.1接口的方法。文档结构包括以下几个部分： 1. **介绍**：这部分明确了文档的目的，即提供CGI/1.1接口的定义和使用指南。同时，它列出了编写文档的需求和规范，以及使用的一些术语。 1.1 **目的**：阐述了CGI的作用，它是如何让外部应用程序与HTTP服务器交互，以便处理用户请求并生成动态网页内容。 1.2 **需求**：详细描述了实现CGI接口所需满足的技术和功能需求。 1.3 **规格**：规定了CGI/1.1接口的具体技术细节，如环境变量、输入输出流、错误处理等。 1.4 **术语**：定义了CGI领域中的关键术语，便于读者理解文档内容。 CGI/1.1接口的核心特征包括以下几点： - **环境变量**：服务器设置一系列环境变量，传递关于HTTP请求的信息，如HTTP头、客户端信息等，给CGI程序使用。 - **标准输入/输出**：CGI程序通过标准输入接收来自服务器的数据，通过标准输出返回结果给服务器，最终由服务器传递给客户端。 - **错误处理**：当CGI程序发生错误时，应有适当的错误报告机制，确保服务器能正确处理异常情况。 - **安全性**：虽然RFC3875文档未经过IETF的安全审查，但在实际部署CGI程序时，必须考虑安全问题，防止恶意攻击和数据泄露。 CGI/1.1在UNIX和其他类UNIX系统上的实现通常涉及到与操作系统shell的交互，利用shell脚本或者编译语言（如C、Perl、Python等）编写CGI程序。这些程序可以读取环境变量，解析HTTP请求，执行业务逻辑，并将响应写入标准输出。《CGI手册RFC3875》是学习CGI编程和理解其工作原理的重要参考资料，它详细定义了CGI/1.1接口的各个方面，对于Web开发者、系统管理员和相关领域的专业人士具有很高的参考价值。

资源推荐

资源详情

资源评论

Network Working Group D. Robinson

Request for Comments: 3875 The Apache Software Foundation

Category: Informational K. Coar

The Apache Software Foundation

October 2004

The Common Gateway Interface (CGI) Version 1.1

Status of this Memo

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

Distribution of this memo is unlimited.

IESG Note

This document is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the

ﬁtness of this document for any purpose, and in particular notes that it has not had IETF review for such things as

security, congestion control or inappropriate interaction with deployed protocols. The RFC Editor has chosen to

publish this document at its discretion. Readers of this document should exercise caution in evaluating its value

for implementation and deployment.

Abstract

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 speciﬁcation deﬁnes the ‘current

practice’ parameters of the ‘CGI/1.1’ interface developed and documented at the U.S. National Centre for Su-

percomputing Applications. This document also deﬁnes the use of the CGI/1.1 interface on UNIX(R) and other,

similar systems.

Robinson & Coar Informational [Page 1]

RFC 3875 CGI Version 1.1 October 2004

Table of Contents

1 Introduction 4

1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.3 Speciﬁcations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.4 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Notational Conventions and Generic Grammar 5

2.1 Augmented BNF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.2 Basic Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.3 URL Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Invoking the Script 7

3.1 Server Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.2 Script Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3.3 The Script-URI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3.4 Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 The CGI Request 9

4.1 Request Meta-Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4.1.1 AUTH_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.1.2 CONTENT_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1.3 CONTENT_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1.4 GATEWAY_INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.1.5 PATH_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.1.6 PATH_TRANSLATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.1.7 QUERY_STRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1.8 REMOTE_ADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.1.9 REMOTE_HOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.1.10 REMOTE_IDENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.1.11 REMOTE_USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.1.12 REQUEST_METHOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.1.13 SCRIPT_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.1.14 SERVER_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.1.15 SERVER_PORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.1.16 SERVER_PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.1.17 SERVER_SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.1.18 Protocol-Speciﬁc Meta-Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.2 Request Message-Body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.3 Request Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.3.1 GET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.3.2 POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.3.3 HEAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.3.4 Protocol-Speciﬁc Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.4 The Script Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Robinson & Coar Informational [Page 2]

RFC 3875 CGI Version 1.1 October 2004

5 NPH Scripts 19

5.1 Identiﬁcation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.2 NPH Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6 CGI Response 20

6.1 Response Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6.2 Response Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6.2.1 Document Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6.2.2 Local Redirect Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6.2.3 Client Redirect Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6.2.4 Client Redirect Response with Document . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6.3 Response Header Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6.3.1 Content-Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6.3.2 Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6.3.3 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6.3.4 Protocol-Speciﬁc Header Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6.3.5 Extension Header Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6.4 Response Message-Body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

7 System Speciﬁcations 25

7.1 AmigaDOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

7.2 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

7.3 EBCDIC/POSIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

8 Implementation 26

8.1 Recommendations for Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

8.2 Recommendations for Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

9 Security Considerations 27

9.1 Safe Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

9.2 Header Fields Containing Sensitive Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

9.3 Data Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

9.4 Information Security Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

9.5 Script Interference with the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

9.6 Data Length and Buffering Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

9.7 Stateless Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

9.8 Relative Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

9.9 Non-parsed Header Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

10 Acknowledgements 29

11 References 29

11.1 Normative References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

11.2 Informative References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

12 Authors’ Addresses 31

13 Full Copyright Statement 32

Robinson & Coar Informational [Page 3]

RFC 3875 CGI Version 1.1 October 2004

1 Introduction

1.1 Purpose

The Common Gateway Interface (CGI) [22] allows an HTTP [1], [4] server and a CGI script to share responsibility

for responding to client requests. The client request comprises a Uniform Resource Identiﬁer (URI) [11], a request

method and various ancillary information about the request provided by the transport protocol.

The CGI deﬁnes the abstract parameters, known as meta-variables, which describe a client’s request. Together

with a concrete programmer interface this speciﬁes a platform-independent interface between the script and the

HTTP server.

The server is responsible for managing connection, data transfer, transport and network issues related to the client

request, whereas the CGI script handles the application issues, such as data access and document processing.

1.2 Requirements

The key words ‘MUST’, ‘MUST NOT’, ‘REQUIRED’, ‘SHALL’, ‘SHALL NOT’, ‘SHOULD’, ‘SHOULD NOT’,

‘RECOMMENDED’, ‘MAY’ and ‘OPTIONAL’ in this document are to be interpreted as described in BCP 14,

RFC 2119 [3].

An implementation is not compliant if it fails to satisfy one or more of the ‘must’ requirements for the protocols it

implements. An implementation that satisﬁes all of the ‘must’ and all of the ‘should’ requirements for its features

is said to be ‘unconditionally compliant’; one that satisﬁes all of the ‘must’ requirements but not all of the ‘should’

requirements for its features is said to be ‘conditionally compliant’.

1.3 Speciﬁcations

Not all of the functions and features of the CGI are deﬁned in the main part of this speciﬁcation. The following

phrases are used to describe the features that are not speciﬁed:

‘system-deﬁned’

The feature may differ between systems, but must be the same for different implementations using the same

system. A system will usually identify a class of operating systems. Some systems are deﬁned in section 7

of this document. New systems may be deﬁned by new speciﬁcations without revision of this document.

‘implementation-deﬁned’

The behaviour of the feature may vary from implementation to implementation; a particular implementation

must document its behaviour.

Robinson & Coar Informational [Page 4]

RFC 3875 CGI Version 1.1 October 2004

1.4 Terminology

This speciﬁcation uses many terms deﬁned in the HTTP/1.1 speciﬁcation [4]; however, the following terms are

used here in a sense which may not accord with their deﬁnitions in that document, or with their common meaning.

‘meta-variable’

A named parameter which carries information from the server to the script. It is not necessarily a variable

in the operating system’s environment, although that is the most common implementation.

‘script’

The software that is invoked by the server according to this interface. It need not be a standalone program,

but could be a dynamically-loaded or shared library, or even a subroutine in the server. It might be a set of

statements interpreted at run-time, as the term ‘script’ is frequently understood, but that is not a requirement

and within the context of this speciﬁcation the term has the broader deﬁnition stated.

‘server’

The application program that invokes the script in order to service requests from the client.

2 Notational Conventions and Generic Grammar

2.1 Augmented BNF

All of the mechanisms speciﬁed in this document are described in both prose and an augmented Backus-Naur

Form (BNF) similar to that used by RFC 822 [13]. Unless stated otherwise, the elements are case-sensitive. This

augmented BNF contains the following constructs:

name = deﬁnition

The name of a rule and its deﬁnition are separated by the equals character (‘=’). Whitespace is only signiﬁ-

cant in that continuation lines of a deﬁnition are indented.

“literal”

Double quotation marks (") surround literal text, except for a literal quotation mark, which is surrounded by

angle-brackets (‘<’ and ‘>’).

rule1 | rule2

Alternative rules are separated by a vertical bar (‘|’).

(rule1 rule2 rule3)

Elements enclosed in parentheses are treated as a single element.

*rule

A rule preceded by an asterisk (‘*’) may have zero or more occurrences. The full form is ‘n*m rule’

indicating at least n and at most m occurrences of the rule. n and m are optional decimal values with default

values of 0 and inﬁnity respectively.

Robinson & Coar Informational [Page 5]

剩余31页未读，继续阅读

评论收藏

内容反馈

自由の翼Az

粉丝: 8
资源: 18

CGI手册RFC3875.pdf

RFC3984.pdf

CGI 开发使用手册.

rfc document

RFC文档PDF

这是CGI编译的文件

CGI的头文件

rfc3551.pdf

WebSocket协议手册(rfc6455中文翻译).pdf

RFC1157.pdf

HTTP2-rfc7540.pdf

rfc2045.pdf

RFC 文档

rfc技术文档

CGI教程

RFC阅读文档中文

RFC中文文档（PDF）

rfc1904.pdf

rfc5416.pdf

RFC3501.rar_RFC3501_rfc 3501_rfc35_rfc3501 pdf_rfc3501.pdf

RTMFP:rfc7425.pdf

rfc7049.pdf

RFC中文文档

中文版RFC文档

rfc3640.pdf

rfc2819.pdf

rfc1631.pdf英文版

最新资源