Network Working Group M. Nottingham
Request for Comments: 4229 J. Mogul
Category: Informational HP Labs
December 2005
Network Working Group M. Nottingham
Request for Comments: 4229 J. Mogul
Category: Informational HP Labs
December 2005
HTTP Header Field Registrations
HTTP头字段注册
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.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document defines the initial contents of a permanent IANA registry for HTTP header fields and a provisional repository for HTTP header fields, per RFC 3864.
本文档根据RFC 3864定义了HTTP头字段的永久IANA注册表和HTTP头字段的临时存储库的初始内容。
Table of Contents
目录
1. Introduction ....................................................4
2. Registration Templates ..........................................4
2.1. Permanent HTTP Header Field Registrations ..................5
2.1.1. Header field: A-IM ....................................7
2.1.2. Header field: Accept ..................................8
2.1.3. Header field: Accept-Additions ........................8
2.1.4. Header field: Accept-Charset ..........................8
2.1.5. Header field: Accept-Encoding .........................9
2.1.6. Header field: Accept-Features .........................9
2.1.7. Header field: Accept-Language .........................9
2.1.8. Header field: Accept-Ranges ..........................10
2.1.9. Header field: Age ....................................10
2.1.10. Header field: Allow .................................10
2.1.11. Header field: Alternates ............................10
2.1.12. Header field: Authentication-Info ...................11
2.1.13. Header field: Authorization .........................11
2.1.14. Header field: C-Ext .................................11
2.1.15. Header field: C-Man .................................12
2.1.16. Header field: C-Opt .................................12
2.1.17. Header field: C-PEP .................................12
2.1.18. Header field: C-PEP-Info ............................13
2.1.19. Header field: Cache-Control .........................13
2.1.20. Header field: Connection ............................13
1. Introduction ....................................................4
2. Registration Templates ..........................................4
2.1. Permanent HTTP Header Field Registrations ..................5
2.1.1. Header field: A-IM ....................................7
2.1.2. Header field: Accept ..................................8
2.1.3. Header field: Accept-Additions ........................8
2.1.4. Header field: Accept-Charset ..........................8
2.1.5. Header field: Accept-Encoding .........................9
2.1.6. Header field: Accept-Features .........................9
2.1.7. Header field: Accept-Language .........................9
2.1.8. Header field: Accept-Ranges ..........................10
2.1.9. Header field: Age ....................................10
2.1.10. Header field: Allow .................................10
2.1.11. Header field: Alternates ............................10
2.1.12. Header field: Authentication-Info ...................11
2.1.13. Header field: Authorization .........................11
2.1.14. Header field: C-Ext .................................11
2.1.15. Header field: C-Man .................................12
2.1.16. Header field: C-Opt .................................12
2.1.17. Header field: C-PEP .................................12
2.1.18. Header field: C-PEP-Info ............................13
2.1.19. Header field: Cache-Control .........................13
2.1.20. Header field: Connection ............................13
2.1.21. Header field: Content-Base ..........................14
2.1.22. Header field: Content-Disposition ...................14
2.1.23. Header field: Content-Encoding ......................14
2.1.24. Header field: Content-ID ............................14
2.1.25. Header field: Content-Language ......................15
2.1.26. Header field: Content-Length ........................15
2.1.27. Header field: Content-Location ......................15
2.1.28. Header field: Content-MD5 ...........................16
2.1.29. Header field: Content-Range .........................16
2.1.30. Header field: Content-Script-Type ...................16
2.1.31. Header field: Content-Style-Type ....................17
2.1.32. Header field: Content-Type ..........................17
2.1.33. Header field: Content-Version .......................17
2.1.34. Header field: Cookie ................................17
2.1.35. Header field: Cookie2 ...............................18
2.1.36. Header field: DAV ...................................18
2.1.37. Header field: Date ..................................18
2.1.38. Header field: Default-Style .........................19
2.1.39. Header field: Delta-Base ............................19
2.1.40. Header field: Depth .................................19
2.1.41. Header field: Derived-From ..........................19
2.1.42. Header field: Destination ...........................20
2.1.43. Header field: Differential-ID .......................20
2.1.44. Header field: Digest ................................20
2.1.45. Header field: ETag ..................................21
2.1.46. Header field: Expect ................................21
2.1.47. Header field: Expires ...............................21
2.1.48. Header field: Ext ...................................22
2.1.49. Header field: From ..................................22
2.1.50. Header field: GetProfile ............................22
2.1.51. Header field: Host ..................................23
2.1.52. Header field: IM ....................................23
2.1.53. Header field: If ....................................23
2.1.54. Header field: If-Match ..............................23
2.1.55. Header field: If-Modified-Since .....................24
2.1.56. Header field: If-None-Match .........................24
2.1.57. Header field: If-Range ..............................24
2.1.58. Header field: If-Unmodified-Since ...................25
2.1.59. Header field: Keep-Alive ............................25
2.1.60. Header field: Label .................................25
2.1.61. Header field: Last-Modified .........................25
2.1.62. Header field: Link ..................................26
2.1.63. Header field: Location ..............................26
2.1.64. Header field: Lock-Token ............................26
2.1.65. Header field: MIME-Version ..........................27
2.1.66. Header field: Man ...................................27
2.1.67. Header field: Max-Forwards ..........................27
2.1.68. Header field: Meter .................................27
2.1.21. Header field: Content-Base ..........................14
2.1.22. Header field: Content-Disposition ...................14
2.1.23. Header field: Content-Encoding ......................14
2.1.24. Header field: Content-ID ............................14
2.1.25. Header field: Content-Language ......................15
2.1.26. Header field: Content-Length ........................15
2.1.27. Header field: Content-Location ......................15
2.1.28. Header field: Content-MD5 ...........................16
2.1.29. Header field: Content-Range .........................16
2.1.30. Header field: Content-Script-Type ...................16
2.1.31. Header field: Content-Style-Type ....................17
2.1.32. Header field: Content-Type ..........................17
2.1.33. Header field: Content-Version .......................17
2.1.34. Header field: Cookie ................................17
2.1.35. Header field: Cookie2 ...............................18
2.1.36. Header field: DAV ...................................18
2.1.37. Header field: Date ..................................18
2.1.38. Header field: Default-Style .........................19
2.1.39. Header field: Delta-Base ............................19
2.1.40. Header field: Depth .................................19
2.1.41. Header field: Derived-From ..........................19
2.1.42. Header field: Destination ...........................20
2.1.43. Header field: Differential-ID .......................20
2.1.44. Header field: Digest ................................20
2.1.45. Header field: ETag ..................................21
2.1.46. Header field: Expect ................................21
2.1.47. Header field: Expires ...............................21
2.1.48. Header field: Ext ...................................22
2.1.49. Header field: From ..................................22
2.1.50. Header field: GetProfile ............................22
2.1.51. Header field: Host ..................................23
2.1.52. Header field: IM ....................................23
2.1.53. Header field: If ....................................23
2.1.54. Header field: If-Match ..............................23
2.1.55. Header field: If-Modified-Since .....................24
2.1.56. Header field: If-None-Match .........................24
2.1.57. Header field: If-Range ..............................24
2.1.58. Header field: If-Unmodified-Since ...................25
2.1.59. Header field: Keep-Alive ............................25
2.1.60. Header field: Label .................................25
2.1.61. Header field: Last-Modified .........................25
2.1.62. Header field: Link ..................................26
2.1.63. Header field: Location ..............................26
2.1.64. Header field: Lock-Token ............................26
2.1.65. Header field: MIME-Version ..........................27
2.1.66. Header field: Man ...................................27
2.1.67. Header field: Max-Forwards ..........................27
2.1.68. Header field: Meter .................................27
2.1.69. Header field: Negotiate .............................28
2.1.70. Header field: Opt ...................................28
2.1.71. Header field: Ordering-Type .........................28
2.1.72. Header field: Overwrite .............................29
2.1.73. Header field: P3P ...................................29
2.1.74. Header field: PEP ...................................29
2.1.75. Header field: PICS-Label ............................30
2.1.76. Header field: Pep-Info ..............................30
2.1.77. Header field: Position ..............................30
2.1.78. Header field: Pragma ................................31
2.1.79. Header field: ProfileObject .........................31
2.1.80. Header field: Protocol ..............................31
2.1.81. Header field: Protocol-Info .........................32
2.1.82. Header field: Protocol-Query ........................32
2.1.83. Header field: Protocol-Request ......................32
2.1.84. Header field: Proxy-Authenticate ....................32
2.1.85. Header field: Proxy-Authentication-Info .............33
2.1.86. Header field: Proxy-Authorization ...................33
2.1.87. Header field: Proxy-Features ........................33
2.1.88. Header field: Proxy-Instruction .....................34
2.1.89. Header field: Public ................................34
2.1.90. Header field: Range .................................34
2.1.91. Header field: Referer ...............................34
2.1.92. Header field: Retry-After ...........................35
2.1.93. Header field: Safe ..................................35
2.1.94. Header field: Security-Scheme .......................35
2.1.95. Header field: Server ................................36
2.1.96. Header field: Set-Cookie ............................36
2.1.97. Header field: Set-Cookie2 ...........................36
2.1.98. Header field: SetProfile ............................36
2.1.99. Header field: SoapAction ............................37
2.1.100. Header field: Status-URI ...........................37
2.1.101. Header field: Surrogate-Capability .................38
2.1.102. Header field: Surrogate-Control ....................38
2.1.103. Header field: TCN ..................................38
2.1.104. Header field: TE ...................................39
2.1.105. Header field: Timeout ..............................39
2.1.106. Header field: Trailer ..............................39
2.1.107. Header field: Transfer-Encoding ....................39
2.1.108. Header field: URI ..................................40
2.1.109. Header field: Upgrade ..............................40
2.1.110. Header field: User-Agent ...........................40
2.1.111. Header field: Variant-Vary .........................41
2.1.112. Header field: Vary .................................41
2.1.113. Header field: Via ..................................41
2.1.114. Header field: WWW-Authenticate .....................41
2.1.115. Header field: Want-Digest ..........................42
2.1.116. Header field: Warning ..............................42
2.1.69. Header field: Negotiate .............................28
2.1.70. Header field: Opt ...................................28
2.1.71. Header field: Ordering-Type .........................28
2.1.72. Header field: Overwrite .............................29
2.1.73. Header field: P3P ...................................29
2.1.74. Header field: PEP ...................................29
2.1.75. Header field: PICS-Label ............................30
2.1.76. Header field: Pep-Info ..............................30
2.1.77. Header field: Position ..............................30
2.1.78. Header field: Pragma ................................31
2.1.79. Header field: ProfileObject .........................31
2.1.80. Header field: Protocol ..............................31
2.1.81. Header field: Protocol-Info .........................32
2.1.82. Header field: Protocol-Query ........................32
2.1.83. Header field: Protocol-Request ......................32
2.1.84. Header field: Proxy-Authenticate ....................32
2.1.85. Header field: Proxy-Authentication-Info .............33
2.1.86. Header field: Proxy-Authorization ...................33
2.1.87. Header field: Proxy-Features ........................33
2.1.88. Header field: Proxy-Instruction .....................34
2.1.89. Header field: Public ................................34
2.1.90. Header field: Range .................................34
2.1.91. Header field: Referer ...............................34
2.1.92. Header field: Retry-After ...........................35
2.1.93. Header field: Safe ..................................35
2.1.94. Header field: Security-Scheme .......................35
2.1.95. Header field: Server ................................36
2.1.96. Header field: Set-Cookie ............................36
2.1.97. Header field: Set-Cookie2 ...........................36
2.1.98. Header field: SetProfile ............................36
2.1.99. Header field: SoapAction ............................37
2.1.100. Header field: Status-URI ...........................37
2.1.101. Header field: Surrogate-Capability .................38
2.1.102. Header field: Surrogate-Control ....................38
2.1.103. Header field: TCN ..................................38
2.1.104. Header field: TE ...................................39
2.1.105. Header field: Timeout ..............................39
2.1.106. Header field: Trailer ..............................39
2.1.107. Header field: Transfer-Encoding ....................39
2.1.108. Header field: URI ..................................40
2.1.109. Header field: Upgrade ..............................40
2.1.110. Header field: User-Agent ...........................40
2.1.111. Header field: Variant-Vary .........................41
2.1.112. Header field: Vary .................................41
2.1.113. Header field: Via ..................................41
2.1.114. Header field: WWW-Authenticate .....................41
2.1.115. Header field: Want-Digest ..........................42
2.1.116. Header field: Warning ..............................42
2.2. Provisional HTTP Header Field Submissions .................43
2.2.1. Header field: Compliance .............................43
2.2.2. Header field: Content-Transfer-Encoding ..............43
2.2.3. Header field: Cost ...................................44
2.2.4. Header field: Message-ID .............................44
2.2.5. Header field: Non-Compliance .........................44
2.2.6. Header field: Optional ...............................44
2.2.7. Header field: Resolution-Hint ........................45
2.2.8. Header field: Resolver-Location ......................45
2.2.9. Header field: SubOK ..................................46
2.2.10. Header field: Subst .................................46
2.2.11. Header field: Title .................................46
2.2.12. Header field: UA-Color ..............................46
2.2.13. Header field: UA-Media ..............................47
2.2.14. Header field: UA-Pixels .............................47
2.2.15. Header field: UA-Resolution .........................48
2.2.16. Header field: UA-Windowpixels .......................48
2.2.17. Header field: Version ...............................48
3. IANA Considerations ............................................49
4. Security Considerations ........................................49
5. Acknowledgements ...............................................49
6. Informative References .........................................49
2.2. Provisional HTTP Header Field Submissions .................43
2.2.1. Header field: Compliance .............................43
2.2.2. Header field: Content-Transfer-Encoding ..............43
2.2.3. Header field: Cost ...................................44
2.2.4. Header field: Message-ID .............................44
2.2.5. Header field: Non-Compliance .........................44
2.2.6. Header field: Optional ...............................44
2.2.7. Header field: Resolution-Hint ........................45
2.2.8. Header field: Resolver-Location ......................45
2.2.9. Header field: SubOK ..................................46
2.2.10. Header field: Subst .................................46
2.2.11. Header field: Title .................................46
2.2.12. Header field: UA-Color ..............................46
2.2.13. Header field: UA-Media ..............................47
2.2.14. Header field: UA-Pixels .............................47
2.2.15. Header field: UA-Resolution .........................48
2.2.16. Header field: UA-Windowpixels .......................48
2.2.17. Header field: Version ...............................48
3. IANA Considerations ............................................49
4. Security Considerations ........................................49
5. Acknowledgements ...............................................49
6. Informative References .........................................49
HTTP/1.0 [3] and HTTP/1.1 [11] define protocol constructs (respectively, the HTTP-header and message-header BNF rules) that are used as message headers. These specifications also define a number of HTTP headers themselves, and they provide for extension through the use of new field-names.
HTTP/1.0[3]和HTTP/1.1[11]定义了用作消息头的协议构造（分别是HTTP头和消息头BNF规则）。这些规范本身还定义了许多HTTP头，并通过使用新字段名提供扩展。
This document defines the initial contents of an IANA registry that catalogs permanent HTTP header field-names, and of an IANA repository that catalogs provisional HTTP header field-names. Both are operated according to Registration Procedures for Message Header Fields [1].
本文档定义了对永久HTTP头字段名称进行编目的IANA注册表和对临时HTTP头字段名称进行编目的IANA存储库的初始内容。这两个字段都是根据消息头字段的注册程序操作的[1]。
Note that neither tracks the syntax or semantics of field-values. Also, while some HTTP headers have different semantics depending on their context (e.g., Cache-Control in requests and responses), both registries consider the HTTP header field-name name space singular.
请注意，两者都不跟踪字段值的语法或语义。此外，虽然一些HTTP报头根据其上下文具有不同的语义（例如，请求和响应中的缓存控制），但两个注册中心都考虑HTTP头字段名称空间奇异。
Also, some contact details listed may no longer be correct.
此外，列出的某些联系方式可能不再正确。
Header field entries are summarized in tabular form for convenience of reference and presented in full in the following sections.
标题字段条目以表格形式汇总，以便于参考，并在以下章节中完整呈现。
Header name Protocol
----------- --------
A-IM http
Accept http
Accept-Additions http
Accept-Charset http
Accept-Encoding http
Accept-Features http
Accept-Language http
Accept-Ranges http
Age http
Allow http
Alternates http
Authentication-Info http
Authorization http
C-Ext http
C-Man http
C-Opt http
C-PEP http
C-PEP-Info http
Cache-Control http
Connection http
Content-Base http
Content-Disposition http
Content-Encoding http
Content-ID http
Content-Language http
Content-Length http
Content-Location http
Content-MD5 http
Content-Range http
Content-Script-Type http
Content-Style-Type http
Content-Type http
Content-Version http
Cookie http
Cookie2 http
DAV http
Date http
Default-Style http
Delta-Base http
Depth http
Derived-From http
Destination http
Differential-ID http
Digest http
Header name Protocol
----------- --------
A-IM http
Accept http
Accept-Additions http
Accept-Charset http
Accept-Encoding http
Accept-Features http
Accept-Language http
Accept-Ranges http
Age http
Allow http
Alternates http
Authentication-Info http
Authorization http
C-Ext http
C-Man http
C-Opt http
C-PEP http
C-PEP-Info http
Cache-Control http
Connection http
Content-Base http
Content-Disposition http
Content-Encoding http
Content-ID http
Content-Language http
Content-Length http
Content-Location http
Content-MD5 http
Content-Range http
Content-Script-Type http
Content-Style-Type http
Content-Type http
Content-Version http
Cookie http
Cookie2 http
DAV http
Date http
Default-Style http
Delta-Base http
Depth http
Derived-From http
Destination http
Differential-ID http
Digest http
ETag http Expect http Expires http Ext http From http GetProfile http Host http IM http If http If-Match http If-Modified-Since http If-None-Match http If-Range http If-Unmodified-Since http Keep-Alive http Label http Last-Modified http Link http Location http Lock-Token http MIME-Version http Man http Max-Forwards http Meter http Negotiate http Opt http Ordering-Type http Overwrite http P3P http PEP http PICS-Label http Pep-Info http Position http Pragma http ProfileObject http Protocol http Protocol-Info http Protocol-Query http Protocol-Request http Proxy-Authenticate http Proxy-Authentication-Info http Proxy-Authorization http Proxy-Features http Proxy-Instruction http Public http Range http Referer http Retry-After http
ETag http Expect http Expires http Expires http Expires http Ext http From http GetProfile http Host http IM http If Match http If Modified自http If None Match http If Range http If Modified自http Keep Alive http Label http Last Modified http Link http Location http Lock Token http MIME Version http Man http Max Forwards http Meter http协商httpOpt http排序类型http Overwrite http P3P http PEP http PICS Label http PEP Info http Position http Pragma http ProfileObject http协议http协议信息http协议查询http协议请求http代理验证http代理验证信息http代理授权http代理功能http代理指令http公共http范围http引用http在http之后重试
Safe http Security-Scheme http Server http Set-Cookie http Set-Cookie2 http SetProfile http SoapAction http Status-URI http Surrogate-Capability http Surrogate-Control http TCN http TE http Timeout http Trailer http Transfer-Encoding http URI http Upgrade http User-Agent http Variant-Vary http Vary http Via http WWW-Authenticate http Want-Digest http Warning http
安全http安全方案http服务器http集Cookie http集Cookie 2 http集配置文件http SoapAction http状态URI http代理功能http代理控制http TCN http代理http超时http尾部http传输编码http URI http升级http用户代理http变体更改http更改http通过http WWW验证http想要摘要http警告http
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC3229 [16]
规范文件：RFC3229[16]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2324 [9]
规范文件：RFC2324[9]
Related information: spoof
相关信息：恶搞
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Andrew H. Mutz (mutz@hpl.hp.com) Koen Holtman (koen@win.tue.nl)
作者/变更控制员：Andrew H.Mutz(mutz@hpl.hp.com)科恩·霍特曼(koen@win.tue.nl)
Specification document(s): RFC2295 [7]
规范文件：RFC2295[7]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Andrew H. Mutz (mutz@hpl.hp.com) Koen Holtman (koen@win.tue.nl)
作者/变更控制员：Andrew H.Mutz(mutz@hpl.hp.com)科恩·霍特曼(koen@win.tue.nl)
Specification document(s): RFC2295 [7]
规范文件：RFC2295[7]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2617 [12]
规范文件：RFC2617[12]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Henrik Frystyk Nielsen (frystyk@microsoft.com) Paul J. Leach (paulle@microsoft.com) Scott Lawrence (lawrence@agranat.com)
作者/变更负责人：亨里克·弗莱斯泰克·尼尔森(frystyk@microsoft.com)保罗·J·利奇(paulle@microsoft.com)斯科特·劳伦斯(lawrence@agranat.com)
Specification document(s): RFC2774 [14]
规范文件：RFC2774[14]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Henrik Frystyk Nielsen (frystyk@microsoft.com) Paul J. Leach (paulle@microsoft.com) Scott Lawrence (lawrence@agranat.com)
作者/变更负责人：亨里克·弗莱斯泰克·尼尔森(frystyk@microsoft.com)保罗·J·利奇(paulle@microsoft.com)斯科特·劳伦斯(lawrence@agranat.com)
Specification document(s): RFC2774 [14]
规范文件：RFC2774[14]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Henrik Frystyk Nielsen (frystyk@microsoft.com) Paul J. Leach (paulle@microsoft.com) Scott Lawrence (lawrence@agranat.com)
作者/变更负责人：亨里克·弗莱斯泰克·尼尔森(frystyk@microsoft.com)保罗·J·利奇(paulle@microsoft.com)斯科特·劳伦斯(lawrence@agranat.com)
Specification document(s): RFC2774 [14]
规范文件：RFC2774[14]
Applicable protocol: http [11]
适用协议：http[11]
Status: deprecated
状态：已弃用
Author/change controller: Henrik Frystyk Nielsen (frystyk@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Dan Connolly (connolly@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Rohit Khare (khare@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Eric Prud'hommeaux (eric@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science
作者/变更负责人：亨里克·弗莱斯泰克·尼尔森(frystyk@w3.org)万维网联盟，麻省理工学院计算机科学实验室Dan Connolly(connolly@w3.org)万维网联盟，麻省理工学院计算机科学实验室Rohit Khare(khare@w3.org)万维网联盟，麻省理工学院计算机科学实验室Eric Prud'hommeaux(eric@w3.org)万维网联盟，麻省理工学院计算机科学实验室
Specification document(s): PEP [29]
规范文件：政治公众人物[29]
Applicable protocol: http [11]
适用协议：http[11]
Status: deprecated
状态：已弃用
Author/change controller: Henrik Frystyk Nielsen (frystyk@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Dan Connolly (connolly@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Rohit Khare (khare@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Eric Prud'hommeaux (eric@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science
作者/变更负责人：亨里克·弗莱斯泰克·尼尔森(frystyk@w3.org)万维网联盟，麻省理工学院计算机科学实验室Dan Connolly(connolly@w3.org)万维网联盟，麻省理工学院计算机科学实验室Rohit Khare(khare@w3.org)万维网联盟，麻省理工学院计算机科学实验室Eric Prud'hommeaux(eric@w3.org)万维网联盟，麻省理工学院计算机科学实验室
Specification document(s): PEP [29]
规范文件：政治公众人物[29]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2068 [4]
规范文件：RFC2068[4]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: Arthur van Hoff (avh@marimba.com) Marimba Inc. John Giannandrea (jg@netscape.com) Netscape Inc. Mark Hapner (mark.hapner@sun.com) Sun Microsystems Inc. Steve Carter (srcarter@novell.com) Novell Inc. Milo Medin (medin@home.net) At Home Corp
作者/变更控制人：阿瑟·范霍夫(avh@marimba.com)马林巴公司(jg@netscape.com)网景公司马克·哈普纳（Mark。hapner@sun.com)太阳微系统公司史蒂夫·卡特(srcarter@novell.com)诺维尔公司(medin@home.net)在家公司
Specification document(s): DRP [20]
规范文件：DRP[20]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: W3C (web-human@w3.org) World Wide Web Consortium
作者/变更控制者：W3C（web-human@w3.org)万维网联盟
Specification document(s): HTML 4 [21]
规格文件：HTML 4[21]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: W3C (web-human@w3.org) World Wide Web Consortium
作者/变更控制者：W3C（web-human@w3.org)万维网联盟
Specification document(s): HTML 4 [21]
规格文件：HTML 4[21]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2068 [4]
规范文件：RFC2068[4]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2965 [15]
规范文件：RFC2965[15]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2965 [15]
规范文件：RFC2965[15]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2518 [10]
规范文件：RFC2518[10]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: W3C (web-human@w3.org) World Wide Web Consortium
作者/变更控制者：W3C（web-human@w3.org)万维网联盟
Specification document(s): HTML 4 [21]
规格文件：HTML 4[21]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC3229 [16]
规范文件：RFC3229[16]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2518 [10]
规范文件：RFC2518[10]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2068 [4]
规范文件：RFC2068[4]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2518 [10]
规范文件：RFC2518[10]
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: Arthur van Hoff (avh@marimba.com) Marimba Inc. John Giannandrea (jg@netscape.com) Netscape Inc. Mark Hapner (mark.hapner@sun.com) Sun Microsystems Inc. Steve Carter (srcarter@novell.com) Novell Inc. Milo Medin (medin@home.net) At Home Corp
作者/变更控制人：阿瑟·范霍夫(avh@marimba.com)马林巴公司(jg@netscape.com)网景公司马克·哈普纳（Mark。hapner@sun.com)太阳微系统公司史蒂夫·卡特(srcarter@novell.com)诺维尔公司(medin@home.net)在家公司
Specification document(s): DRP [20]
规范文件：DRP[20]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC3230 [17]
规范文件：RFC3230[17]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Henrik Frystyk Nielsen (frystyk@microsoft.com) Paul J. Leach (paulle@microsoft.com) Scott Lawrence (lawrence@agranat.com)
作者/变更负责人：亨里克·弗莱斯泰克·尼尔森(frystyk@microsoft.com)保罗·J·利奇(paulle@microsoft.com)斯科特·劳伦斯(lawrence@agranat.com)
Specification document(s): RFC2774 [14]
规范文件：RFC2774[14]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: Pat Hensley (hensley@firefly.net) FireFly Network, Inc. Max Metral (max@firefly.net) FireFly Network, Inc. Upendra Shardanand (shard@firefly.net) FireFly Network, Inc. Donna Converse (converse@netscape.com) Netscape Communications Mike Myers (mmyers@verisign.com) Verisign, Inc.
作者/变更控制员：帕特·亨斯利(hensley@firefly.net)萤火虫网络公司Max Metral(max@firefly.net)萤火虫网络公司Upendra Shardanand(shard@firefly.net)萤火虫网络公司唐娜匡威(converse@netscape.com)网景通讯公司迈克·迈尔斯(mmyers@verisign.com)威瑞信公司。
Specification document(s): OPS over HTTP [22]
规范文件：HTTP上的OPS[22]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC3229 [16]
规范文件：RFC3229[16]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2518 [10]
规范文件：RFC2518[10]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2068 [4]
规范文件：RFC2068[4]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC3253 [18]
规范文件：RFC3253[18]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2068 [4]
规范文件：RFC2068[4]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2518 [10]
规范文件：RFC2518[10]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Henrik Frystyk Nielsen (frystyk@microsoft.com) Paul J. Leach (paulle@microsoft.com) Scott Lawrence (lawrence@agranat.com)
作者/变更负责人：亨里克·弗莱斯泰克·尼尔森(frystyk@microsoft.com)保罗·J·利奇(paulle@microsoft.com)斯科特·劳伦斯(lawrence@agranat.com)
Specification document(s): RFC2774 [14]
规范文件：RFC2774[14]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2227 [6]
规范文件：RFC2227[6]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Andrew H. Mutz (mutz@hpl.hp.com) Koen Holtman (koen@win.tue.nl)
作者/变更控制员：Andrew H.Mutz(mutz@hpl.hp.com)科恩·霍特曼(koen@win.tue.nl)
Specification document(s): RFC2295 [7]
规范文件：RFC2295[7]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Henrik Frystyk Nielsen (frystyk@microsoft.com) Paul J. Leach (paulle@microsoft.com) Scott Lawrence (lawrence@agranat.com)
作者/变更负责人：亨里克·弗莱斯泰克·尼尔森(frystyk@microsoft.com)保罗·J·利奇(paulle@microsoft.com)斯科特·劳伦斯(lawrence@agranat.com)
Specification document(s): RFC2774 [14]
规范文件：RFC2774[14]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC3648 [19]
规范文件：RFC3648[19]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2518 [10]
规范文件：RFC2518[10]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: W3C (web-human@w3.org) World Wide Web Consortium
作者/变更控制者：W3C（web-human@w3.org)万维网联盟
Specification document(s): P3P [23]
规范文件：P3P[23]
Applicable protocol: http [11]
适用协议：http[11]
Status: deprecated
状态：已弃用
Author/change controller: Henrik Frystyk Nielsen (frystyk@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Dan Connolly (connolly@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Rohit Khare (khare@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Eric Prud'hommeaux (eric@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science
作者/变更负责人：亨里克·弗莱斯泰克·尼尔森(frystyk@w3.org)万维网联盟，麻省理工学院计算机科学实验室Dan Connolly(connolly@w3.org)万维网联盟，麻省理工学院计算机科学实验室Rohit Khare(khare@w3.org)万维网联盟，麻省理工学院计算机科学实验室Eric Prud'hommeaux(eric@w3.org)万维网联盟，麻省理工学院计算机科学实验室
Specification document(s): PEP [29]
规范文件：政治公众人物[29]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: W3C (web-human@w3.org) World Wide Web Consortium
作者/变更控制者：W3C（web-human@w3.org)万维网联盟
Specification document(s): PICSLabels [24]
规范文件：PICSLabels[24]
Applicable protocol: http [11]
适用协议：http[11]
Status: deprecated
状态：已弃用
Author/change controller: Henrik Frystyk Nielsen (frystyk@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Dan Connolly (connolly@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Rohit Khare (khare@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science Eric Prud'hommeaux (eric@w3.org) World Wide Web Consortium, MIT Laboratory for Computer Science
作者/变更负责人：亨里克·弗莱斯泰克·尼尔森(frystyk@w3.org)万维网联盟，麻省理工学院计算机科学实验室Dan Connolly(connolly@w3.org)万维网联盟，麻省理工学院计算机科学实验室Rohit Khare(khare@w3.org)万维网联盟，麻省理工学院计算机科学实验室Eric Prud'hommeaux(eric@w3.org)万维网联盟，麻省理工学院计算机科学实验室
Specification document(s): PEP [29]
规范文件：政治公众人物[29]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC3648 [19]
规范文件：RFC3648[19]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: Pat Hensley (hensley@firefly.net) FireFly Network, Inc. Max Metral (max@firefly.net) FireFly Network, Inc. Upendra Shardanand (shard@firefly.net) FireFly Network, Inc. Donna Converse (converse@netscape.com) Netscape Communications Mike Myers (mmyers@verisign.com) Verisign, Inc.
作者/变更控制员：帕特·亨斯利(hensley@firefly.net)萤火虫网络公司Max Metral(max@firefly.net)萤火虫网络公司Upendra Shardanand(shard@firefly.net)萤火虫网络公司唐娜匡威(converse@netscape.com)网景通讯公司迈克·迈尔斯(mmyers@verisign.com)威瑞信公司。
Specification document(s): OPS over HTTP [22]
规范文件：HTTP上的OPS[22]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: W3C (web-human@w3.org) World Wide Web Consortium
作者/变更控制者：W3C（web-human@w3.org)万维网联盟
Specification document(s): PICSLabels [24]
规范文件：PICSLabels[24]
Applicable protocol: http [11]
适用协议：http[11]
Status: deprecated
状态：已弃用
Author/change controller: Don Eastlake (dee@cybercash.com) Rohit Khare (khare@w3.org) Jim Miller (jmiller@w3.org)
作者/变更控制员：Don Eastlake(dee@cybercash.com)罗希特·哈雷(khare@w3.org)吉姆·米勒(jmiller@w3.org)
Specification document(s): Selecting Payment Mechanisms [26]
规范文件：选择支付机制[26]
Applicable protocol: http [11]
适用协议：http[11]
Status: deprecated
状态：已弃用
Author/change controller: Don Eastlake (dee@cybercash.com) Rohit Khare (khare@w3.org) Jim Miller (jmiller@w3.org)
作者/变更控制员：Don Eastlake(dee@cybercash.com)罗希特·哈雷(khare@w3.org)吉姆·米勒(jmiller@w3.org)
Specification document(s): Selecting Payment Mechanisms [26]
规范文件：选择支付机制[26]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: W3C (web-human@w3.org) World Wide Web Consortium
作者/变更控制者：W3C（web-human@w3.org)万维网联盟
Specification document(s): PICSLabels [24]
规范文件：PICSLabels[24]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2617 [12]
规范文件：RFC2617[12]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: Phillip M. Hallam-Baker (hallam@w3.org) W3C
作者/变更控制人：Phillip M.Hallam Baker(hallam@w3.org)W3C
Specification document(s): Proxy Notification [27]
规范文件：代理通知[27]
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: Phillip M. Hallam-Baker (hallam@w3.org) W3C
作者/变更控制人：Phillip M.Hallam Baker(hallam@w3.org)W3C
Specification document(s): Proxy Notification [27]
规范文件：代理通知[27]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2068 [4]
规范文件：RFC2068[4]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Koen Holtman (koen@win.tue.nl)
作者/变更控制员：Koen Holtman(koen@win.tue.nl)
Specification document(s): RFC2310 [8]
规范文件：RFC2310[8]
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Eric Rescorla (ekr@rtfm.com) A. Schiffman (ams@terisa.com)
作者/变更控制员：Eric Rescorla(ekr@rtfm.com)A.希夫曼(ams@terisa.com)
Specification document(s): RFC2660 [13]
规范文件：RFC2660[13]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2109 [5]
规范文件：RFC2109[5]
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2965 [15]
规范文件：RFC2965[15]
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: Pat Hensley (hensley@firefly.net) FireFly Network, Inc. Max Metral (max@firefly.net) FireFly Network, Inc. Upendra Shardanand (shard@firefly.net) FireFly Network, Inc. Donna Converse (converse@netscape.com) Netscape Communications Mike Myers (mmyers@verisign.com) Verisign, Inc.
作者/变更控制员：帕特·亨斯利(hensley@firefly.net)萤火虫网络公司Max Metral(max@firefly.net)萤火虫网络公司Upendra Shardanand(shard@firefly.net)萤火虫网络公司唐娜匡威(converse@netscape.com)网景通讯公司迈克·迈尔斯(mmyers@verisign.com)威瑞信公司。
Specification document(s): OPS over HTTP [22]
规范文件：HTTP上的OPS[22]
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: Don Box (dbox@develop.com) DevelopMentor David Ehnebuske (davide@us.ibm.com) IBM Gopal Kakivaya (gopalk@microsoft.com) Microsoft Andrew Layman (andrewl@microsoft.com) Microsoft Noah Mendelsohn (Noah_Mendelsohn@lotus.com) Lotus Development Corp. Hernik Frystyk Nielsen (frystyk@microsoft.com) Microsoft Satish Thatte (satisht@microsoft.com) Microsoft Dave Winer (dave@userland.com) UserLand Software, Inc.
作者/更改控制器：Don Box(dbox@develop.com)大卫·埃内布斯克的发展(davide@us.ibm.com)IBM Gopal Kakivaya(gopalk@microsoft.com)微软安德鲁·莱曼(andrewl@microsoft.com)微软诺亚·门德尔松_Mendelsohn@lotus.com)莲花发展公司Hernik Frystyk Nielsen(frystyk@microsoft.com)微软Satish Thatte(satisht@microsoft.com)微软戴夫·温纳(dave@userland.com)UserLand软件公司。
Specification document(s): SOAP [28]
规范文件：SOAP[28]
2.1.100. Header field: Status-URI
2.1.100. 标题字段：状态URI
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2518 [10]
规范文件：RFC2518[10]
2.1.101. Header field: Surrogate-Capability
2.1.101. 标题字段：代理功能
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: Mark Nottingham (mnot@akamai.com) Akamai Xiang Liu (xiang.liu@oracle.com) Oracle
作者/变更控制人：马克·诺丁汉(mnot@akamai.com)刘翔（刘翔）。liu@oracle.com)神谕
Specification document(s): edge-arch [25]
规范文件：边拱[25]
2.1.102. Header field: Surrogate-Control
2.1.102. 标题字段：代理控件
Applicable protocol: http [11]
适用协议：http[11]
Status: informational
状态：信息性
Author/change controller: Mark Nottingham (mnot@akamai.com) Akamai Xiang Liu (xiang.liu@oracle.com) Oracle
作者/变更控制人：马克·诺丁汉(mnot@akamai.com)刘翔（刘翔）。liu@oracle.com)神谕
Specification document(s): edge-arch [25]
规范文件：边拱[25]
2.1.103. Header field: TCN
2.1.103. 标题字段：TCN
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Andrew H. Mutz (mutz@hpl.hp.com) Koen Holtman (koen@win.tue.nl)
作者/变更控制员：Andrew H.Mutz(mutz@hpl.hp.com)科恩·霍特曼(koen@win.tue.nl)
Specification document(s): RFC2295 [7]
规范文件：RFC2295[7]
2.1.104. Header field: TE
2.1.104. 标题字段：TE
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
2.1.105. Header field: Timeout
2.1.105. 标题字段：超时
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2518 [10]
规范文件：RFC2518[10]
2.1.106. Header field: Trailer
2.1.106. 标题字段：拖车
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
2.1.107. Header field: Transfer-Encoding
2.1.107. 标题字段：传输编码
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
2.1.108. Header field: URI
2.1.108. 标题字段：URI
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2068 [4]
规范文件：RFC2068[4]
2.1.109. Header field: Upgrade
2.1.109. 标题字段：升级
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
2.1.110. Header field: User-Agent
2.1.110. 标题字段：用户代理
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
2.1.111. Header field: Variant-Vary
2.1.111. 标题字段：变量不同
Applicable protocol: http [11]
适用协议：http[11]
Status: experimental
现状：实验性
Author/change controller: Andrew H. Mutz (mutz@hpl.hp.com) Koen Holtman (koen@win.tue.nl)
作者/变更控制员：Andrew H.Mutz(mutz@hpl.hp.com)科恩·霍特曼(koen@win.tue.nl)
Specification document(s): RFC2295 [7]
规范文件：RFC2295[7]
2.1.112. Header field: Vary
2.1.112. 标题字段：更改
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
2.1.113. Header field: Via
2.1.113. 标题字段：Via
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
2.1.114. Header field: WWW-Authenticate
2.1.114. 标题字段：WWW-Authenticate
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
2.1.115. Header field: Want-Digest
2.1.115. 标题字段：想要摘要
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC3230 [17]
规范文件：RFC3230[17]
2.1.116. Header field: Warning
2.1.116. 标题字段：警告
Applicable protocol: http [11]
适用协议：http[11]
Status: standard
状态：标准
Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF(iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC2616 [11]
规范文件：RFC2616[11]
Header name Protocol
----------- --------
Compliance http
Content-Transfer-Encoding http
Cost http
Message-ID http
Non-Compliance http
Optional http
Resolution-Hint http
Resolver-Location http
SubOK http
Subst http
Title http
UA-Color http
UA-Media http
UA-Pixels http
UA-Resolution http
UA-Windowpixels http
Version http
Header name Protocol
----------- --------
Compliance http
Content-Transfer-Encoding http
Cost http
Message-ID http
Non-Compliance http
Optional http
Resolution-Hint http
Resolver-Location http
SubOK http
Subst http
Title http
UA-Color http
UA-Media http
UA-Pixels http
UA-Resolution http
UA-Windowpixels http
Version http
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Jeffrey C. Mogul (mogul@wrl.dec.com) Western Research Laboratory, Digital Equipment Corporation Josh Cohen (josh@netscape.com) Netscape Communications Corporation Scott Lawrence (lawrence@agranat.com) Agranat Systems, Inc.
作者/变更负责人：杰弗里·C·莫格尔(mogul@wrl.dec.com)数字设备公司西方研究实验室Josh Cohen(josh@netscape.com)网景通讯公司斯科特·劳伦斯(lawrence@agranat.com)阿格兰特系统公司。
Specification document(s): OPTIONS messages [31]
规范文件：选项信息[31]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Tim Berners-Lee (timbl@w3.org) MIT Laboratory for Computer Science
作者/变更负责人：Tim Berners Lee(timbl@w3.org)麻省理工学院计算机科学实验室
Specification document(s): Object Headers [2]
规范文档：对象标题[2]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Tim Berners-Lee (timbl@w3.org) MIT Laboratory for Computer Science
作者/变更负责人：Tim Berners Lee(timbl@w3.org)麻省理工学院计算机科学实验室
Specification document(s): Object Headers [2]
规范文档：对象标题[2]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Tim Berners-Lee (timbl@w3.org) MIT Laboratory for Computer Science
作者/变更负责人：Tim Berners Lee(timbl@w3.org)麻省理工学院计算机科学实验室
Specification document(s): Object Headers [2]
规范文档：对象标题[2]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Jeffrey C. Mogul (mogul@wrl.dec.com) Western Research Laboratory, Digital Equipment Corporation Josh Cohen (josh@netscape.com) Netscape Communications Corporation Scott Lawrence (lawrence@agranat.com) Agranat Systems, Inc.
作者/变更负责人：杰弗里·C·莫格尔(mogul@wrl.dec.com)数字设备公司西方研究实验室Josh Cohen(josh@netscape.com)网景通讯公司斯科特·劳伦斯(lawrence@agranat.com)阿格兰特系统公司。
Specification document(s): OPTIONS messages [31]
规范文件：选项信息[31]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: John Mallery (jcma@ai.mit.edu) MIT Artificial Intelligence Laboratory Lewis Girod (girod@lcs.mit.edu) MIT Laboratory for Computer Science Benjie Chen (benjie@lcs.mit.edu) MIT Laboratory for Computer Science Henrik Frystyk Nielsen (frystyk@w3.org) World Wide Web Consortium
作者/变更控制员：John Mallery(jcma@ai.mit.edu)麻省理工学院人工智能实验室刘易斯·吉罗德(girod@lcs.mit.edu)麻省理工学院计算机科学实验室陈本杰(benjie@lcs.mit.edu)麻省理工学院计算机科学实验室Henrik Frystyk Nielsen(frystyk@w3.org)万维网联盟
Specification document(s): WIRE [32]
规范文件：电线[32]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: John Mallery (jcma@ai.mit.edu) MIT Artificial Intelligence Laboratory Lewis Girod (girod@lcs.mit.edu) MIT Laboratory for Computer Science Benjie Chen (benjie@lcs.mit.edu) MIT Laboratory for Computer Science Henrik Frystyk Nielsen (frystyk@w3.org) World Wide Web Consortium
作者/变更控制员：John Mallery(jcma@ai.mit.edu)麻省理工学院人工智能实验室刘易斯·吉罗德(girod@lcs.mit.edu)麻省理工学院计算机科学实验室陈本杰(benjie@lcs.mit.edu)麻省理工学院计算机科学实验室Henrik Frystyk Nielsen(frystyk@w3.org)万维网联盟
Specification document(s): WIRE [32]
规范文件：电线[32]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: John Mallery (jcma@ai.mit.edu) MIT Artificial Intelligence Laboratory Lewis Girod (girod@lcs.mit.edu) MIT Laboratory for Computer Science Benjie Chen (benjie@lcs.mit.edu) MIT Laboratory for Computer Science Henrik Frystyk Nielsen (frystyk@w3.org) World Wide Web Consortium
作者/变更控制员：John Mallery(jcma@ai.mit.edu)麻省理工学院人工智能实验室刘易斯·吉罗德(girod@lcs.mit.edu)麻省理工学院计算机科学实验室陈本杰(benjie@lcs.mit.edu)麻省理工学院计算机科学实验室Henrik Frystyk Nielsen(frystyk@w3.org)万维网联盟
Specification document(s): WIRE [32]
规范文件：电线[32]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Jeffrey C. Mogul (mogul@wrl.dec.com) Western Research Laboratory, Digital Equipment Corporation Arthur van Hoff (avh@marimba.com) Marimba, Inc.
作者/变更负责人：杰弗里·C·莫格尔(mogul@wrl.dec.com)数字设备公司西部研究实验室Arthur van Hoff(avh@marimba.com)马林巴公司。
Specification document(s): Duplicate Suppression [33]
规范文件：重复抑制[33]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Jeffrey C. Mogul (mogul@wrl.dec.com) Western Research Laboratory, Digital Equipment Corporation Arthur van Hoff (avh@marimba.com) Marimba, Inc.
作者/变更负责人：杰弗里·C·莫格尔(mogul@wrl.dec.com)数字设备公司西部研究实验室Arthur van Hoff(avh@marimba.com)马林巴公司。
Specification document(s): Duplicate Suppression [33]
规范文件：重复抑制[33]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Tim Berners-Lee (timbl@w3.org) MIT Laboratory for Computer Science
作者/变更负责人：Tim Berners Lee(timbl@w3.org)麻省理工学院计算机科学实验室
Specification document(s): Object Headers [2]
规范文档：对象标题[2]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Larry Masinter (LMM@acm.org) Adobe Systems Lou Montulli (montulli@netscape.com) Netscape Communications Corp. Andrew H. Mutz (mutz@hpl.hp.com) Hewlett-Packard Company
作者/变更控制员：拉里·马森特(LMM@acm.org)Adobe Systems Lou Montulli(montulli@netscape.com)网景通讯公司安德鲁H穆茨(mutz@hpl.hp.com)惠普公司
Specification document(s): UA Attributes [30]
规范文件：UA属性[30]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Larry Masinter (LMM@acm.org) Adobe Systems Lou Montulli (montulli@netscape.com) Netscape Communications Corp. Andrew H. Mutz (mutz@hpl.hp.com) Hewlett-Packard Company
作者/变更控制员：拉里·马森特(LMM@acm.org)Adobe Systems Lou Montulli(montulli@netscape.com)网景通讯公司安德鲁H穆茨(mutz@hpl.hp.com)惠普公司
Specification document(s): UA Attributes [30]
规范文件：UA属性[30]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Larry Masinter (LMM@acm.org) Adobe Systems Lou Montulli (montulli@netscape.com) Netscape Communications Corp. Andrew H. Mutz (mutz@hpl.hp.com) Hewlett-Packard Company
作者/变更控制员：拉里·马森特(LMM@acm.org)Adobe Systems Lou Montulli(montulli@netscape.com)网景通讯公司安德鲁H穆茨(mutz@hpl.hp.com)惠普公司
Specification document(s): UA Attributes [31]
规范文件：UA属性[31]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Larry Masinter (LMM@acm.org) Adobe Systems Lou Montulli (montulli@netscape.com) Netscape Communications Corp. Andrew H. Mutz (mutz@hpl.hp.com) Hewlett-Packard Company
作者/变更控制员：拉里·马森特(LMM@acm.org)Adobe Systems Lou Montulli(montulli@netscape.com)网景通讯公司安德鲁H穆茨(mutz@hpl.hp.com)惠普公司
Specification document(s): UA Attributes [30]
规范文件：UA属性[30]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Larry Masinter (LMM@acm.org) Adobe Systems Lou Montulli (montulli@netscape.com) Netscape Communications Corp. Andrew H. Mutz (mutz@hpl.hp.com) Hewlett-Packard Company
作者/变更控制员：拉里·马森特(LMM@acm.org)Adobe Systems Lou Montulli(montulli@netscape.com)网景通讯公司安德鲁H穆茨(mutz@hpl.hp.com)惠普公司
Specification document(s): UA Attributes [30]
规范文件：UA属性[30]
Applicable protocol: http [11]
适用协议：http[11]
Status: provisional
现状：临时
Author/change controller: Tim Berners-Lee (timbl@w3.org) MIT Laboratory for Computer Science
作者/变更负责人：Tim Berners Lee(timbl@w3.org)麻省理工学院计算机科学实验室
Specification document(s): Object Headers [2]
规范文档：对象标题[2]
This specification provides initial registrations of HTTP header fields in the "Permanent Message Header Field Registry", defined by Registration Procedures for Message Header Fields [1].
本规范提供了“永久消息头字段注册表”中HTTP头字段的初始注册，该注册表由消息头字段的注册过程定义[1]。
It also provides initial submissions of HTTP header fields in the "Provisional Message Header Field Repository", defined by the same document.
它还提供了由同一文档定义的“临时消息头字段存储库”中HTTP头字段的初始提交。
No security considerations are introduced by this document beyond those already inherent in use of the HTTP header fields referenced.
除了在使用所引用的HTTP头字段时已经固有的安全注意事项外，本文档没有引入其他安全注意事项。
The authors would like to thank Graham Klyne for his work in defining the message header registries, his input and help in preparing this document, and the registry generation software.
作者要感谢Graham Klyne在定义消息头注册表方面所做的工作、在编写本文档时的投入和帮助，以及注册表生成软件。
[1] Klyne, G., Nottingham, M., and J. Mogul, "Registration Procedures for Message Header Fields", BCP 90, RFC 3864, September 2004.
[1] Klyne，G.，Nottingham，M.和J.Mogul，“消息头字段的注册程序”，BCP 90，RFC 3864，2004年9月。
[2] Berners-Lee, T., "Object Header lines in HTTP", May 1994, <http://www.w3.org/Protocols/HTTP/Object_Headers.html>.
[2] Berners Lee，T.，“HTTP中的对象头行”，1994年5月<http://www.w3.org/Protocols/HTTP/Object_Headers.html>.
[3] Berners-Lee, T., Fielding, R., and H. Nielsen, "Hypertext Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996.
[3] Berners Lee，T.，Fielding，R.，和H.Nielsen，“超文本传输协议——HTTP/1.0”，RFC 1945，1996年5月。
[4] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2068, January 1997.
[4] 菲尔丁，R.，盖蒂斯，J.，莫格尔，J.，尼尔森，H.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC 2068，1997年1月。
[5] Kristol, D. and L. Montulli, "HTTP State Management Mechanism", RFC 2109, February 1997.
[5] Kristol，D.和L.Montulli，“HTTP状态管理机制”，RFC 2109，1997年2月。
[6] Mogul, J. and P. Leach, "Simple Hit-Metering and Usage-Limiting for HTTP", RFC 2227, October 1997.
[6] Mogul，J.和P.Leach，“HTTP的简单命中计量和使用限制”，RFC 2227，1997年10月。
[7] Holtman, K. and A. Mutz, "Transparent Content Negotiation in HTTP", RFC 2295, March 1998.
[7] Holtman，K.和A.Mutz，“HTTP中的透明内容协商”，RFC 2295，1998年3月。
[8] Holtman, K., "The Safe Response Header Field", RFC 2310, April 1998.
[8] Holtman，K.，“安全响应标题字段”，RFC 2310，1998年4月。
[9] Masinter, L., "Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)", RFC 2324, April 1998.
[9] Masinter，L.，“超文本咖啡壶控制协议（HTCPCP/1.0）”，RFC 23241998年4月。
[10] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. Jensen, "HTTP Extensions for Distributed Authoring -- WEBDAV", RFC 2518, February 1999.
[10] Goland，Y.，Whitehead，E.，Faizi，A.，Carter，S.，和D.Jensen，“分布式创作的HTTP扩展——WEBDAV”，RFC25181999年2月。
[11] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[11] 菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC2616，1999年6月。
[12] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, "HTTP Authentication: Basic and Digest Access Authentication", RFC 2617, June 1999.
[12] Franks，J.，Hallam Baker，P.，Hostetler，J.，Lawrence，S.，Leach，P.，Lootonen，A.，和L.Stewart，“HTTP认证：基本和摘要访问认证”，RFC 26171999年6月。
[13] Rescorla, E. and A. Schiffman, "The Secure HyperText Transfer Protocol", RFC 2660, August 1999.
[13] Rescorla，E.和A.Schiffman，“安全超文本传输协议”，RFC 2660，1999年8月。
[14] Nielsen, H., Leach, P., and S. Lawrence, "An HTTP Extension Framework", RFC 2774, February 2000.
[14] Nielsen，H.，Leach，P.，和S.Lawrence，“HTTP扩展框架”，RFC 27742000年2月。
[15] Kristol, D. and L. Montulli, "HTTP State Management Mechanism", RFC 2965, October 2000.
[15] Kristol，D.和L.Montulli，“HTTP状态管理机制”，RFC 29652000年10月。
[16] Mogul, J., Krishnamurthy, B., Douglis, F., Feldmann, A., Goland, Y., van Hoff, A., and D. Hellerstein, "Delta encoding in HTTP", RFC 3229, January 2002.
[16] Mogul，J.，Krishnamurthy，B.，Douglis，F.，Feldmann，A.，Goland，Y.，van Hoff，A.，和D.Hellerstein，“HTTP中的增量编码”，RFC 3229，2002年1月。
[17] Mogul, J. and A. Van Hoff, "Instance Digests in HTTP", RFC 3230, January 2002.
[17] Mogul，J.和A.Van Hoff，“HTTP中的实例摘要”，RFC 3230，2002年1月。
[18] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. Whitehead, "Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)", RFC 3253, March 2002.
[18] Clemm，G.，Amsden，J.，Ellison，T.，Kaler，C.，和J.Whitehead，“WebDAV的版本控制扩展（Web分布式创作和版本控制）”，RFC 3253，2002年3月。
[19] Whitehead, J. and J. Reschke, Ed., "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol", RFC 3648, December 2003.
[19] Whitehead，J.和J.Reschke，Ed.，“Web分布式创作和版本控制（WebDAV）有序收集协议”，RFC 3648，2003年12月。
[20] Hoff, A., Payne, J., Hapner, M., Carter, S., and M. Medin, "The HTTP Distribution and Replication Protocol", W3C NOTE NOTE-drp-19970825, August 1997.
[20] Hoff，A.，Payne，J.，Hapner，M.，Carter，S.，和M.Medin，“HTTP分发和复制协议”，W3C NOTE-drp-199708252997年8月。
[21] Raggett, D., Hors, A., and I. Jacobs, "HTML 4.01 Specification", W3C REC REC-html401-19991224, December 1999.
[21] Raggett，D.，Hors，A.，和I.Jacobs，“HTML4.01规范”，W3C REC REC-html401-19991224，1999年12月。
[22] Hensley, P., Metral, M., Shardanand, U., Converse, D., and M. Myers, "Implementation of OPS Over HTTP", W3C NOTE NOTE-OPS-OverHTTP, June 1997.
[22] Hensley，P.，Metral，M.，Shardanand，U.，Converse，D.，和M.Myers，“通过HTTP实现OPS”，W3C注释OPS OverHTTP，1997年6月。
[23] Marchiori, M., "The Platform for Privacy Preferences 1.0 (P3P1.0) Specification", W3C REC REC-P3P-20020416, April 2002.
[23] Marchiori，M.，“隐私偏好平台1.0（P3P1.0）规范”，W3C REC REC-P3P-20020416，2002年4月。
[24] Krauskopf, T., Miller, J., Resnick, P., and W. Treese, "PICS 1.1 Label Distribution -- Label Syntax and Communication Protocols", W3C REC REC-PICS-labels-961031, October 1996.
[24] Krauskopf，T.，Miller，J.，Resnick，P.，和W.Treese，“PICS 1.1标签分发——标签语法和通信协议”，W3C REC-PICS-labels-9610311996年10月。
[25] Nottingham, M. and X. Liu, "Edge Architecture Specification", W3C NOTE NOTE-edge-arch-20010804, August 2001.
[25] Nottingham，M.和X.Liu，“边缘架构规范”，W3C注释NOTE-Edge-arch-200108042001年8月。
[26] Chung, E. and D. Dardailler, "White Paper: Joint Electronic Payment Initiative", W3C NOTE NOTE-jepi-970519, May 1997.
[26] Chung，E.和D.Dardailler，“白皮书：联合电子支付倡议”，W3C NOTE-jepi-970519，1997年5月。
[27] Hallam-Baker, P., "Notification for Proxy Caches", W3C NOTE WD-proxy-960221, February 1996.
[27] Hallam Baker，P.，“代理缓存通知”，W3C注释WD-Proxy-960221，1996年2月。
[28] Box, D., Ehnebuske, D., Kakivaya, G., Layman, A., Mendelsohn, N., Nielsen, H., Thatte, S., and D. Winer, "Simple Object Access Protocol (SOAP) 1.1", W3C NOTE NOTE-SOAP-20000508, May 2000.
[28] Box，D.，Ehnebuske，D.，Kakivaya，G.，Layman，A.，Mendelsohn，N.，Nielsen，H.，Thatte，S.，和D.Winer，“简单对象访问协议（SOAP）1.1”，W3C NOTE-SOAP-20000508，2000年5月。
[29] Connolly, D., Prod'hommeaux, E., Nielsen, H., and R. Khare, "PEP Specification: an Extension Mechanism for HTTP", Nov 1998, <http://www.w3.org/TR/WD-http-pep>.
[29] Connolly，D.，Prod'hommeaux，E.，Nielsen，H.，和R.Khare，“PEP规范：HTTP的扩展机制”，1998年11月<http://www.w3.org/TR/WD-http-pep>.
[30] Masinter, L., Montulli, L., and A. Mutz, "User-Agent Display Attributes Headers", Work in Progress, November 1996.
[30] Masinter，L.，Montulli，L.，和A.Mutz，“用户代理显示属性标题”，正在进行的工作，1996年11月。
[31] Mogul, J., Cohen, J., and S. Lawrence, "Specification of HTTP/1.1 OPTIONS messages", Work in Progress, August 1997.
[31] Mogul，J.，Cohen，J.，和S.Lawrence，“HTTP/1.1选项消息规范”，正在进行的工作，1997年8月。
[32] Girod, L., Chen, B., Henrik, H., and J. Mallery, "WIRE - W3 Identifier Resolution Extensions", Work in Progress, March 1998.
[32] Girod，L.，Chen，B.，Henrik，H.，和J.Mallery，“WIRE-W3标识符解析扩展”，正在进行的工作，1998年3月。
[33] Mogul, J. and A. van Hoff, "Duplicate Suppression in HTTP", Work in Progress, April 1998.
[33] Mogul，J.和A.van Hoff，“HTTP中的重复抑制”，正在进行的工作，1998年4月。
Authors' Addresses
作者地址
Mark Nottingham
马克诺丁汉
EMail: mnot@pobox.com
URI: http://www.mnot.net/
EMail: mnot@pobox.com
URI: http://www.mnot.net/
Jeffrey C. Mogul HP Labs 1501 Page Mill Road Palo Alto, CA 94304 US
美国加利福尼亚州帕洛阿尔托米尔路1501号杰弗里·C·莫卧儿惠普实验室，邮编94304
EMail: JeffMogul@acm.org
EMail: JeffMogul@acm.org
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。