Internet Engineering Task Force (IETF) S. Moonesamy, Ed.
Request for Comments: 6694 August 2012
Category: Informational
ISSN: 2070-1721
Internet Engineering Task Force (IETF) S. Moonesamy, Ed.
Request for Comments: 6694 August 2012
Category: Informational
ISSN: 2070-1721
The "about" URI Scheme
“关于”URI方案
Abstract
摘要
This document describes the "about" URI scheme, which is widely used by Web browsers and some other applications to designate access to their internal resources, such as settings, application information, hidden built-in functionality, and so on.
本文档描述了“关于”URI方案，Web浏览器和一些其他应用程序广泛使用该方案来指定对其内部资源的访问，如设置、应用程序信息、隐藏的内置功能等。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6694.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6694.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
2. URI Scheme Specification ........................................2
2.1. URI Scheme Syntax ..........................................2
2.2. URI Scheme Semantics .......................................3
2.2.1. Well-Known "about" URIs .............................3
2.3. Encoding Considerations ....................................3
3. "about:blank" ...................................................3
4. Security Considerations .........................................3
5. IANA Considerations .............................................4
5.1. URI Scheme Registration ....................................4
5.2. A Registry for Well-Known Tokens ...........................5
5.2.1. Registration Procedure ..............................5
6. References ......................................................6
6.1. Normative References .......................................6
6.2. Informative References .....................................6
Appendix A. Acknowledgments ........................................7
1. Introduction ....................................................2
2. URI Scheme Specification ........................................2
2.1. URI Scheme Syntax ..........................................2
2.2. URI Scheme Semantics .......................................3
2.2.1. Well-Known "about" URIs .............................3
2.3. Encoding Considerations ....................................3
3. "about:blank" ...................................................3
4. Security Considerations .........................................3
5. IANA Considerations .............................................4
5.1. URI Scheme Registration ....................................4
5.2. A Registry for Well-Known Tokens ...........................5
5.2.1. Registration Procedure ..............................5
6. References ......................................................6
6.1. Normative References .......................................6
6.2. Informative References .....................................6
Appendix A. Acknowledgments ........................................7
This document describes the "about" Uniform Resource Identifier (URI) scheme. The "about" URI scheme is currently widely used by Web browsers to designate access to their internal resources, such as settings, application information, and so-called "Easter eggs" (i.e., a hidden feature or joke in an application).
本文档描述了“关于”统一资源标识符（URI）方案。“关于”URI方案目前被Web浏览器广泛用于指定对其内部资源的访问，如设置、应用程序信息和所谓的“复活节彩蛋”（即应用程序中的隐藏功能或笑话）。
The "about" URI syntactically conforms to the <about-uri> rule below, expressed using the Augmented Backus-Naur Form (ABNF) [RFC5234]:
“about”URI在语法上符合下面的<about URI>规则，使用增广的Backus-Naur形式（ABNF）[RFC5234]表示：
about-uri = "about:" about-token [ about-query ] [ about-fragment ]
about-token = *pchar
about-query = "?" query
about-fragment = "#" fragment
pchar = <as specified in RFC 3986, Appendix A>
query = <as specified in RFC 3986, Appendix A>
fragment = <as specified in RFC 3986, Appendix A>
about-uri = "about:" about-token [ about-query ] [ about-fragment ]
about-token = *pchar
about-query = "?" query
about-fragment = "#" fragment
pchar = <as specified in RFC 3986, Appendix A>
query = <as specified in RFC 3986, Appendix A>
fragment = <as specified in RFC 3986, Appendix A>
The resource that is referenced by a particular "about" URI is denoted by the <about-token> part of the URI. It is not a hierarchical element for a naming authority. The <about-query> part specifies additional information about its handling and/or the information that should be returned by the resource referenced by the URI.
由特定“about”URI引用的资源由URI的<about token>部分表示。它不是命名机构的分层元素。<about query>部分指定有关其处理的附加信息和/或URI引用的资源应返回的信息。
It is impossible to specify a binding between all the possible tokens and the semantics of "about" URIs that would contain such tokens. Therefore, the resource referenced by the URI is generally considered to be specific to a Web browser implementation.
不可能在所有可能的标记和包含此类标记的“about”uri的语义之间指定绑定。因此，URI引用的资源通常被认为是特定于Web浏览器实现的。
Some <about-token>s have been reserved, as the behavior of the resource that is referenced is well-known (well-known tokens).
一些<about token>s已被保留，因为所引用资源的行为是众所周知的（众所周知的令牌）。
A well-known "about" URI is a URI that has a well-known token as its <about-token> part. It is recommended that such URIs be handled in accordance with the specification referenced in the "about" URI Tokens registry (see Section 5.2).
众所周知的“about”URI是一个URI，它的<about-token>部分包含一个众所周知的令牌。建议按照“关于”URI令牌注册表中引用的规范处理此类URI（参见第5.2节）。
Well-known "about" URIs are intended to be registered when there is a need to codify the behavior of a particular <about-token>.
当需要对特定<about token>的行为进行编码时，将注册众所周知的“about”uri。
"about" URIs are subject to encoding rules as defined in RFC 3986 [RFC3986].
“关于”URI遵循RFC 3986[RFC3986]中定义的编码规则。
This document defines one well-known token: "blank". The "about:blank" URI refers to a resource represented in the browser by a blank page.
本文档定义了一个众所周知的标记：“blank”。“about:blank”URI是指浏览器中由空白页面表示的资源。
Security considerations for URIs are discussed in Section 7 of RFC 3986 [RFC3986]. However, most of those provisions do not apply to the "about" URI scheme, as they are mainly scoped to schemes used in the Internet.
在RFC 3986[RFC3986]的第7节中讨论了URI的安全注意事项。然而，这些规定大多不适用于“关于”URI方案，因为它们主要适用于互联网中使用的方案。
"about" URIs can sometimes refer to sensitive information, such as user passwords stored in a cache, or parameters that, if changed, could affect a user's data. The application therefore needs to ensure that the user's data is secured and no threats are imposed by "about" URIs.
“关于”URI有时可能引用敏感信息，例如存储在缓存中的用户密码，或者如果更改可能会影响用户数据的参数。因此，应用程序需要确保用户的数据是安全的，并且“关于”URI不会造成任何威胁。
The "about" URI scheme has been registered in the "Permanent URI Schemes" registry. The information below is provided according to the guidelines from RFC 4395 [RFC4395]:
“关于”URI方案已在“永久URI方案”注册表中注册。以下信息是根据RFC 4395[RFC4395]的指南提供的：
URI scheme name: about
URI方案名称：关于
Status: Permanent
地位：永久
URI scheme syntax: See Section 2.1 of RFC 6694.
URI方案语法：参见RFC 6694的第2.1节。
URI scheme semantics: See Section 2.2 of RFC 6694.
URI方案语义：参见RFC6694的第2.2节。
URI scheme encoding considerations: See Section 2.3 of RFC 6694.
URI方案编码注意事项：参见RFC 6694的第2.3节。
Applications that use the scheme: "about" URIs are predominantly used by Web browsers.
使用“关于”URI的应用程序主要由Web浏览器使用。
Security considerations: See Section 4 of RFC 6694.
安全注意事项：见RFC 6694第4节。
Contact: IETF Applications Area Directors
<app-ads@tools.ietf.org>
Contact: IETF Applications Area Directors
<app-ads@tools.ietf.org>
Author/Change controller: IESG <iesg@ietf.org> (on behalf of the
IETF)
Author/Change controller: IESG <iesg@ietf.org> (on behalf of the
IETF)
References: See Section 6 of RFC 6694.
参考：见RFC 6694第6节。
This document creates the '"about" URI Tokens' registry.
本文档创建“关于”URI令牌注册表。
The registry entries consist of three fields: Token, Description, and Reference. The Token field has to conform to <about-token> production as defined in Section 2.1. The initial assignment is as follows:
注册表项由三个字段组成：标记、描述和引用。令牌字段必须符合第2.1节中定义的<about Token>生产。初步任务如下：
+--------------+------------------------------------+-------------+
| Token | Description | Reference |
+--------------+------------------------------------+-------------+
| blank | The about:blank URI references a | RFC 6694 |
| | blank page. | |
+--------------+------------------------------------+-------------+
+--------------+------------------------------------+-------------+
| Token | Description | Reference |
+--------------+------------------------------------+-------------+
| blank | The about:blank URI references a | RFC 6694 |
| | blank page. | |
+--------------+------------------------------------+-------------+
The registration policy for this registry is "First Come First Served", as described in RFC 5226 [RFC5226]. The registrant of the token should provide the information mentioned in the following registration template:
如RFC 5226[RFC5226]所述，此注册表的注册策略为“先到先得”。令牌的注册人应提供以下注册模板中提到的信息：
o Registered token: The desired well-known token to be used in "about" URIs.
o 注册令牌：在“关于”URI中使用的所需的已知令牌。
o Intended usage: A short description of how "about" URIs with the registered token are handled, including information about the referenced resource.
o 预期用途：简短描述如何处理带有注册令牌的“关于”URI，包括有关引用资源的信息。
o Contact/change controller: Person (including contact information) authorized to change this registration.
o 联系人/变更控制员：有权变更此注册的人员（包括联系信息）。
o Specification: A stable reference to a document that specifies the registered "about" URI. The question of interoperability does not arise. The key motivation is to have a reference to a specification documenting well-known behavior of the "about" URI in Web browsers. As a rule of thumb, if the behavior is common to two or more Web browser implementations, it can be considered well-known. An existing assignment may be duplicated if the registered token is used in more than one Web browser implementation.
o 规范：对文档的稳定引用，指定已注册的“about”URI。互操作性问题并不存在。关键的动机是引用一个规范，该规范记录了Web浏览器中“about”URI的众所周知的行为。根据经验，如果这种行为在两个或多个Web浏览器实现中是常见的，则可以认为是众所周知的。如果注册的令牌在多个Web浏览器实现中使用，则现有分配可能会重复。
The following is a template for the "blank" token:
以下是“空白”令牌的模板：
o Registered token: blank
o 注册令牌：空白
o Intended usage: The about:blank URI references a blank page.
o 预期用途：about:blank URI引用空白页面。
o Contact/change controller: IESG <iesg@ietf.org> (on behalf of the IETF).
o 联系人/变更控制员：IESG<iesg@ietf.org>（代表IETF）。
o Specification: RFC 6694
o 规格：RFC6694
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5234]Crocker，D.，Ed.，和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Registration Procedures for New URI Schemes", BCP 35, RFC 4395, February 2006.
[RFC4395]Hansen，T.，Hardie，T.，和L.Masinter，“新URI方案的指南和注册程序”，BCP 35，RFC 4395，2006年2月。
This document was formed from a previous draft document initially authored by Lachlan Hunt and Joseph Holsten. Additionally, the contributions of Frank Ellermann and Alexey Melnikov are gratefully acknowledged. Barry Leiba and Murray Kucherawy deserve special credit for providing a great amount of text that was used in this document.
本文件由Lachlan Hunt和Joseph Holsten最初编写的前一份文件草稿构成。此外，感谢Frank Ellermann和Alexey Melnikov的贡献。巴里·莱巴（Barry Leiba）和默里·库奇拉维（Murray Kucherawy）值得特别赞扬，因为他们提供了本文档中使用的大量文本。
Lachlan Hunt and Mykyta Yevstifeyev edited previous versions of this document. Tim Bray and John Klensin provided suggestions about how to improve the document.
Lachlan Hunt和Mykyta Yevstifeyev编辑了本文件的早期版本。蒂姆·布雷（Tim Bray）和约翰·克莱辛（John Klesins）就如何改进该文件提出了建议。
Author's Address
作者地址
S. Moonesamy (editor) 76 Ylang Ylang Avenue Quatre Bornes Mauritius
S.Moonesamy（编辑）76依兰依兰大道四分之一博尔内斯毛里求斯
EMail: sm+ietf@elandsys.com
EMail: sm+ietf@elandsys.com