6694
INFORMATIONAL
The "about" URI Scheme
Authors: S. Moonesamy
Date: August 2012
Area: app
Working Group: appsawg
Stream: IETF
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. This document is not an Internet Standards Track specification; it is published for informational purposes.
RFC 6694
INFORMATIONAL
Internet Engineering Task Force (IETF) S. Moonesamy, Ed.
Request for Comments: 6694 August 2012
Category: Informational
ISSN: 2070-1721
<span class="h1">The "about" URI Scheme</span>
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.
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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6694">http://www.rfc-editor.org/info/rfc6694</a>.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Moonesamy Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6694">RFC 6694</a> The "about" URI Scheme August 2012</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. URI Scheme Specification ........................................<a href="#page-2">2</a>
<a href="#section-2.1">2.1</a>. URI Scheme Syntax ..........................................<a href="#page-2">2</a>
<a href="#section-2.2">2.2</a>. URI Scheme Semantics .......................................<a href="#page-3">3</a>
<a href="#section-2.2.1">2.2.1</a>. Well-Known "about" URIs .............................<a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. Encoding Considerations ....................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. "about:blank" ...................................................<a href="#page-3">3</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-3">3</a>
<a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-4">4</a>
<a href="#section-5.1">5.1</a>. URI Scheme Registration ....................................<a href="#page-4">4</a>
<a href="#section-5.2">5.2</a>. A Registry for Well-Known Tokens ...........................<a href="#page-5">5</a>
<a href="#section-5.2.1">5.2.1</a>. Registration Procedure ..............................<a href="#page-5">5</a>
<a href="#section-6">6</a>. References ......................................................<a href="#page-6">6</a>
<a href="#section-6.1">6.1</a>. Normative References .......................................<a href="#page-6">6</a>
<a href="#section-6.2">6.2</a>. Informative References .....................................<a href="#page-6">6</a>
<a href="#appendix-A">Appendix A</a>. Acknowledgments ........................................<a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
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).
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. URI Scheme Specification</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. URI Scheme Syntax</span>
The "about" URI syntactically conforms to the <about-uri> rule below,
expressed using the Augmented Backus-Naur Form (ABNF) [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>]:
about-uri = "about:" about-token [ about-query ] [ about-fragment ]
about-token = *pchar
about-query = "?" query
about-fragment = "#" fragment
pchar = <as specified in <a href="./rfc3986#appendix-A">RFC 3986, Appendix A</a>>
query = <as specified in <a href="./rfc3986#appendix-A">RFC 3986, Appendix A</a>>
fragment = <as specified in <a href="./rfc3986#appendix-A">RFC 3986, Appendix A</a>>
<span class="grey">Moonesamy Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6694">RFC 6694</a> The "about" URI Scheme August 2012</span>
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. URI Scheme Semantics</span>
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.
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.
<span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. Well-Known "about" URIs</span>
Some <about-token>s have been reserved, as the behavior of the
resource that is referenced is well-known (well-known tokens).
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 <a href="#section-5.2">Section 5.2</a>).
Well-known "about" URIs are intended to be registered when there is a
need to codify the behavior of a particular <about-token>.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Encoding Considerations</span>
"about" URIs are subject to encoding rules as defined in <a href="./rfc3986">RFC 3986</a>
[<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. "about:blank"</span>
This document defines one well-known token: "blank". The
"about:blank" URI refers to a resource represented in the browser by
a blank page.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
Security considerations for URIs are discussed in <a href="./rfc3986#section-7">Section 7 of
RFC 3986</a> [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]. However, most of those provisions do not apply
to the "about" URI scheme, as they are mainly scoped to schemes used
in the Internet.
<span class="grey">Moonesamy Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6694">RFC 6694</a> The "about" URI Scheme August 2012</span>
"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.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. URI Scheme Registration</span>
The "about" URI scheme has been registered in the "Permanent URI
Schemes" registry. The information below is provided according to
the guidelines from <a href="./rfc4395">RFC 4395</a> [<a href="./rfc4395" title=""Guidelines and Registration Procedures for New URI Schemes"">RFC4395</a>]:
URI scheme name: about
Status: Permanent
URI scheme syntax: See <a href="./rfc6694#section-2.1">Section 2.1 of RFC 6694</a>.
URI scheme semantics: See <a href="./rfc6694#section-2.2">Section 2.2 of RFC 6694</a>.
URI scheme encoding considerations: See <a href="./rfc6694#section-2.3">Section 2.3 of RFC 6694</a>.
Applications that use the scheme: "about" URIs are predominantly
used by Web browsers.
Security considerations: See <a href="./rfc6694#section-4">Section 4 of RFC 6694</a>.
Contact: IETF Applications Area Directors
<app-ads@tools.ietf.org>
Author/Change controller: IESG <iesg@ietf.org> (on behalf of the
IETF)
References: See <a href="./rfc6694#section-6">Section 6 of RFC 6694</a>.
<span class="grey">Moonesamy Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc6694">RFC 6694</a> The "about" URI Scheme August 2012</span>
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. A Registry for Well-Known Tokens</span>
This document creates the '"about" URI Tokens' registry.
The registry entries consist of three fields: Token, Description, and
Reference. The Token field has to conform to <about-token>
production as defined in <a href="#section-2.1">Section 2.1</a>. The initial assignment is as
follows:
+--------------+------------------------------------+-------------+
| Token | Description | Reference |
+--------------+------------------------------------+-------------+
| blank | The about:blank URI references a | <a href="./rfc6694">RFC 6694</a> |
| | blank page. | |
+--------------+------------------------------------+-------------+
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Registration Procedure</span>
The registration policy for this registry is "First Come First
Served", as described in <a href="./rfc5226">RFC 5226</a> [<a href="./rfc5226" title="">RFC5226</a>]. The registrant of the
token should provide the information mentioned in the following
registration template:
o Registered token: The desired well-known token to be used in
"about" URIs.
o Intended usage: A short description of how "about" URIs with the
registered token are handled, including information about the
referenced resource.
o Contact/change controller: Person (including contact information)
authorized to change this registration.
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.
<span class="grey">Moonesamy Informational [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc6694">RFC 6694</a> The "about" URI Scheme August 2012</span>
The following is a template for the "blank" token:
o Registered token: blank
o Intended usage: The about:blank URI references a blank page.
o Contact/change controller: IESG <iesg@ietf.org> (on behalf of the
IETF).
o Specification: <a href="./rfc6694">RFC 6694</a>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
<a href="./rfc3986">RFC 3986</a>, January 2005.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed., and P. Overell, "Augmented BNF for
Syntax Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
January 2008.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC4395">RFC4395</a>] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
Registration Procedures for New URI Schemes", <a href="https://www.rfc-editor.org/bcp/bcp35">BCP 35</a>,
<a href="./rfc4395">RFC 4395</a>, February 2006.
<span class="grey">Moonesamy Informational [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc6694">RFC 6694</a> The "about" URI Scheme August 2012</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Acknowledgments</span>
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 and Mykyta Yevstifeyev edited previous versions of this
document. Tim Bray and John Klensin provided suggestions about how
to improve the document.
Author's Address
S. Moonesamy (editor)
76 Ylang Ylang Avenue
Quatre Bornes
Mauritius
EMail: [email protected]
Moonesamy Informational [Page 7]
Annotations
Select text to annotate