summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc6694.txt
blob: 7050c38a86568ac63ab2e54cc5a39f464b2ad997 (plain) (blame)
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
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
Internet Engineering Task Force (IETF)                 S. Moonesamy, Ed.
Request for Comments: 6694                                   August 2012
Category: Informational
ISSN: 2070-1721


                         The "about" URI Scheme

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 Section 2 of RFC 5741.

   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.

Copyright Notice

   Copyright (c) 2012 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.  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.






Moonesamy                     Informational                     [Page 1]
^L
RFC 6694                 The "about" URI Scheme              August 2012


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

   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).

2.  URI Scheme Specification

2.1.  URI Scheme Syntax

   The "about" URI syntactically conforms to the <about-uri> rule below,
   expressed using the Augmented Backus-Naur Form (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>










Moonesamy                     Informational                     [Page 2]
^L
RFC 6694                 The "about" URI Scheme              August 2012


2.2.  URI Scheme Semantics

   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.

2.2.1.  Well-Known "about" URIs

   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 Section 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>.

2.3.  Encoding Considerations

   "about" URIs are subject to encoding rules as defined in RFC 3986
   [RFC3986].

3.  "about:blank"

   This document defines one well-known token: "blank".  The
   "about:blank" URI refers to a resource represented in the browser by
   a blank page.

4.  Security Considerations

   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.







Moonesamy                     Informational                     [Page 3]
^L
RFC 6694                 The "about" URI Scheme              August 2012


   "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.

5.  IANA Considerations

5.1.  URI Scheme Registration

   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 scheme name: about

      Status: Permanent

      URI scheme syntax: See Section 2.1 of RFC 6694.

      URI scheme semantics: See Section 2.2 of RFC 6694.

      URI scheme encoding considerations: See Section 2.3 of RFC 6694.

      Applications that use the scheme: "about" URIs are predominantly
         used by Web browsers.

      Security considerations: See Section 4 of RFC 6694.

      Contact: IETF Applications Area Directors
         <app-ads@tools.ietf.org>

      Author/Change controller: IESG <iesg@ietf.org> (on behalf of the
         IETF)

      References: See Section 6 of RFC 6694.















Moonesamy                     Informational                     [Page 4]
^L
RFC 6694                 The "about" URI Scheme              August 2012


5.2.  A Registry for Well-Known Tokens

   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 Section 2.1.  The initial assignment is as
   follows:

   +--------------+------------------------------------+-------------+
   | Token        | Description                        | Reference   |
   +--------------+------------------------------------+-------------+
   | blank        | The about:blank URI references a   | RFC 6694    |
   |              | blank page.                        |             |
   +--------------+------------------------------------+-------------+

5.2.1.  Registration Procedure

   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:

   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.









Moonesamy                     Informational                     [Page 5]
^L
RFC 6694                 The "about" URI Scheme              August 2012


   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:  RFC 6694

6.  References

6.1.  Normative References

   [RFC3986]   Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
               Resource Identifier (URI): Generic Syntax", STD 66,
               RFC 3986, January 2005.

   [RFC5226]   Narten, T. and H. Alvestrand, "Guidelines for Writing an
               IANA Considerations Section in RFCs", BCP 26, RFC 5226,
               May 2008.

   [RFC5234]   Crocker, D., Ed., and P. Overell, "Augmented BNF for
               Syntax Specifications: ABNF", STD 68, RFC 5234,
               January 2008.

6.2.  Informative References

   [RFC4395]   Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
               Registration Procedures for New URI Schemes", BCP 35,
               RFC 4395, February 2006.



















Moonesamy                     Informational                     [Page 6]
^L
RFC 6694                 The "about" URI Scheme              August 2012


Appendix A.  Acknowledgments

   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: sm+ietf@elandsys.com






























Moonesamy                     Informational                     [Page 7]
^L