/
draft-holsten-about-uri-scheme-00.txt
280 lines (163 loc) · 8.63 KB
/
draft-holsten-about-uri-scheme-00.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
Network Working Group J. Holsten
Internet-Draft N/A
Intended status: Informational L. Hunt
Expires: July 31, 2009 Opera Software, ASA.
January 27, 2009
The 'about' URI scheme
draft-holsten-about-uri-scheme-00
Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 31, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
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.
Abstract
This document specifies the URI (Uniform Resource Identifier) scheme
Holsten & Hunt Expires July 31, 2009 [Page 1]
Internet-Draft The 'about' URI scheme January 2009
"about". About URIs are designed to be an internal, application-
level identifier. Unlike many other URI schemes, the resolution of,
and resources represented by, about URIs are left entirely to each
individual application.
1. Introduction
An about URI is designed to be used internally by applications for
almost any desired purpose. Such URIs have commonly been used by web
browsers for proving access to built-in functionality, such as
application preferences and settings, information about the
application, or "easter eggs".
About URIs are more memorable than an equivalent urn or tag URI.
Using an http URI would not only be less memorable, but also longer
and semantically confusing. While any number of existing schemes
could be used to identify such resources, about URIs have become the
de facto standard. Browsers already use the about scheme. The
about:blank (Section 3.1) URI is ubiquitous, and some browsers also
provide other resources with the about scheme, including those in
Section 3.2.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. URI Syntax
The general syntax of a about URI, in ABNF [RFC5234] is:
abouturi = "about:" segment
where "segment" is imported from [RFC3986]. About URIs are always
escaped, as per [RFC3986].
No relative URI syntax is defined.
3. Resolving About URIs
In general, applications are free to resolve any about URI to any
resource, either internal or external, or redirect to an alternative
URI, with about:blank being the only exception.
As about URIs are designed to be internal to each application, there
is no expectation of any URI, except about:blank, returning the same
resource among different applications. However, it is worth noting
that some conventions have arisen for providing particular
functionality via common about URIs.
Holsten & Hunt Expires July 31, 2009 [Page 2]
Internet-Draft The 'about' URI scheme January 2009
Because about URIs identify application specific information,
applications should not need to retrieve remote information for such
a resource.
The about:blank URI is the only about URI reserved by this
specification.
3.1. about:blank
This URI identifies an empty resource. If the application may use a
document of MIME type 'text/html' and character encoding 'UTF-8',
about:blank SHOULD be represented with an empty document. Other
representations are not defined.
3.2. Examples
The following examples illustrate some known URIs supported by
existing applications. They are not guaranteed to be resolvable by
every application.
about:config Commonly provides access to application preferences and
settings
about:cache Commonly provides access to information about resources
stored in the browsers cache.
about:plugins Commonly provides access to information about
installed plugins
about:mozilla An easter egg supported by Mozilla showing a passage
from the fictional Book of Mozilla
about:internets An easter egg supported by Google Chrome depicting
the internet as a series of tubes.
4. Acknowledgements
This document was made possible thanks to the input of Henri Sivonen,
Ian Hickson and Larry Masinter.
5. Security Considerations
There is no guarantee that an application will understand any about
URI provided to it. An about URI may not resolve to the expected
resource. If the reference is unlikely to resolve correctly, the
reference should be accompanied by an explanation or alternatives.
Some applications are known to display arbitrary HTML following the
Holsten & Hunt Expires July 31, 2009 [Page 3]
Internet-Draft The 'about' URI scheme January 2009
scheme. Applications should be cautious when accessing an about URI.
An application should not execute or display information in an about
URI. About URIs should not cause the application to modify any data.
Applications should not use about URIs to access, or erase files or
other sensitive information.
About URIs may identify resources which show sensitive information.
This data SHOULD NOT be exposed in about URIs.>
6. IANA Considerations
This specification requests the IANA permanently register the about
URI scheme as specified in this document and summarized in the
following template, per [RFC4395]:
URI scheme name: about
Status: Provisional
URI scheme syntax: See Section 2
URI scheme semantics: See Section 1
Encoding considerations: Percent-encoding is allowed in 'segment'
components (see Section 2)
Intended usage: See Section 1
Applications and/or protocols that use this URI scheme name: Any
applications that use URIs as identifiers for private resources,
such as web browsers.
Interoperability considerations: Applications are only required to
support about:blank, and may choose to interpret other about URIs
differently. Other about URIs should only be expected to work
correctly within the same application.
Security considerations: See Section 5
Relevant publications: None
Contact: Joseph Holsten (joseph@josephholsten.com)
Author/Change controller: Joseph Holsten
7. References
Holsten & Hunt Expires July 31, 2009 [Page 4]
Internet-Draft The 'about' URI scheme January 2009
7.1. Normative References
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
7.2. Informative References
[RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
Registration Procedures for New URI Schemes", BCP 115,
RFC 4395, February 2006.
Authors' Addresses
Joseph Anthony Pasquale Holsten
N/A
EMail: joseph@josephholsten.com
URI: http://josephholsten.com
Lachlan Hunt
Opera Software, ASA.
EMail: lachlan.hunt@lachy.id.au
URI: http://lachy.id.au/
Holsten & Hunt Expires July 31, 2009 [Page 5]