Annotation of 2006/webapi/XMLHttpRequest/Overview.src.html, revision 1.252
1.248 avankest 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
1.1 avankest 2: <html lang="en-US">
3: <head>
1.207 avankest 4: <title>XMLHttpRequest</title>
1.16 avankest 5: <style type="text/css">
1.117 avankest 6: pre.idl { border:solid thin; background:#eee; color:#000; padding:0.5em }
1.16 avankest 7: pre.idl :link, pre.idl :visited { color:inherit; background:transparent }
1.58 avankest 8: pre code { color:inherit; background:transparent }
1.16 avankest 9: div.example { margin-left:1em; padding-left:1em; border-left:double; color:#222; background:#fcfcfc }
1.89 avankest 10: .note { margin-left:2em; font-weight:bold; font-style:italic; color:#008000 }
1.16 avankest 11: p.note::before { content:"Note: " }
1.203 avankest 12: .XXX { padding:.5em; border:solid #f00 }
13: p.XXX::before { content:"Issue: " }
1.119 avankest 14: dl.switch { padding-left:2em }
1.248 avankest 15: dl.switch > dt { text-indent:-1.5em }
16: dl.switch > dt:before { content:'21円AA'; padding:0 0.5em 0 0; display:inline-block; width:1em; text-align:right; line-height:0.5em }
1.16 avankest 17: em.ct { text-transform:lowercase; font-variant:small-caps; font-style:normal }
18: dfn { font-weight:bold; font-style:normal }
19: code { color:orangered }
20: code :link, code :visited { color:inherit }
1.203 avankest 21: hr:not(.top) { display:block; background:none; border:none; padding:0; margin:2em 0; height:auto }
22: table { border-collapse:collapse; border-style:hidden hidden none hidden }
23: table thead { border-bottom:solid }
24: table tbody th:first-child { border-left:solid }
25: table td, table th { border-left:solid; border-right:solid; border-bottom:solid thin; vertical-align:top; padding:0.2em }
1.16 avankest 26: </style>
1.147 avankest 27: <link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-[STATUS]">
1.1 avankest 28: </head>
29: <body>
30: <div class="head">
31: <p><a href="http://www.w3.org/"><img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home"></a></p>
1.12 avankest 32:
1.229 avankest 33: <h1 class="head" id="the-xmlhttprequest-object">XMLHttpRequest</h1>
1.248 avankest 34:
1.12 avankest 35:
1.149 avankest 36: <h2 class="no-num no-toc" id="w3c-doctype">[LONGSTATUS] [DATE: 3 August 2002]</h2>
1.12 avankest 37:
1.1 avankest 38: <dl>
1.10 avankest 39: <dt>This Version:</dt>
1.246 avankest 40: <dd><a href="[VERSION]/">http://www.w3.org/TR/[YEAR]/ED-XMLHttpRequest-[CDATE]/</a></dd>
1.14 avankest 41:
1.10 avankest 42: <dt>Latest Version:</dt>
1.1 avankest 43: <dd><a href="http://www.w3.org/TR/XMLHttpRequest/">http://www.w3.org/TR/XMLHttpRequest/</a></dd>
1.203 avankest 44:
1.189 avankest 45: <dt>Latest Editor Version:</dt>
46: <dd><a href="http://dev.w3.org/2006/webapi/XMLHttpRequest/">http://dev.w3.org/2006/webapi/XMLHttpRequest/</a></dd>
1.14 avankest 47:
1.10 avankest 48: <dt>Previous Versions:</dt>
1.248 avankest 49:
1.231 avankest 50: <dd><a href="http://www.w3.org/TR/2009/WD-XMLHttpRequest-20090820/">http://www.w3.org/TR/2009/WD-XMLHttpRequest-20090820/</a></dd>
1.173 avankest 51: <dd><a href="http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415/">http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415/</a></dd>
1.154 avankest 52: <dd><a href="http://www.w3.org/TR/2007/WD-XMLHttpRequest-20071026/">http://www.w3.org/TR/2007/WD-XMLHttpRequest-20071026/</a></dd>
1.133 avankest 53: <dd><a href="http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070618/">http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070618/</a></dd>
1.58 avankest 54: <dd><a href="http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070227/">http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070227/</a></dd>
1.22 avankest 55: <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060927/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060927/</a></dd>
1.1 avankest 56: <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060619/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060619/</a></dd>
57: <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/</a></dd>
1.248 avankest 58:
59:
1.14 avankest 60:
1.1 avankest 61: <dt>Editor:</dt>
62: <dd><a href="http://annevankesteren.nl/">Anne van Kesteren</a>
63: (<a href="http://www.opera.com/">Opera Software ASA</a>)
64: <<a href="mailto:annevk@opera.com">annevk@opera.com</a>></dd>
65: </dl>
1.14 avankest 66:
1.1 avankest 67: <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
1.229 avankest 68: © 2009
1.51 avankest 69: <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup>
70: (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
71: <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
72: <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C
73: <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
74: <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
75: and
76: <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
77: use</a> rules apply.</p>
1.1 avankest 78: </div>
1.12 avankest 79:
1.1 avankest 80: <hr>
1.12 avankest 81:
1.1 avankest 82: <h2 class="no-num no-toc" id="specabstract">Abstract</h2>
1.10 avankest 83:
1.248 avankest 84:
85:
1.229 avankest 86: <p>The XMLHttpRequest specification defines an API
1.207 avankest 87: that provides scripted client functionality for transferring data between
88: a client and a server.</p>
1.248 avankest 89:
1.12 avankest 90:
1.1 avankest 91: <h2 class="no-num no-toc" id="sotd">Status of this Document</h2>
1.12 avankest 92:
1.1 avankest 93: <p><em>This section describes the status of this document at the time of its
1.36 avankest 94: publication. Other documents may supersede this document. A list of current
95: W3C publications and the latest revision of this technical report can be
96: found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>
1.117 avankest 97: at http://www.w3.org/TR/.</em></p>
1.36 avankest 98:
1.248 avankest 99: <p>This is the [DATE: 3 August 2002] <!--Last Call Working Draft-->[LONGSTATUS] of
100: XMLHttpRequest. Please send comments to
101: <a href="mailto:public-webapps@w3.org?subject=[XHR]%20">public-webapps@w3.org</a>
1.207 avankest 102: (<a href="http://lists.w3.org/Archives/Public/public-webapps/">archived</a>)
1.248 avankest 103: with <samp>[XHR]</samp> at the start of the subject line.</p>
1.51 avankest 104:
1.47 avankest 105: <p>This document is produced by the
1.248 avankest 106: <a href="http://www.w3.org/2008/webapps/">Web Applications</a> (WebApps) Working Group.
107: The WebApps Working Group is part of the
1.207 avankest 108: <a href="http://www.w3.org/2006/rwc/Activity">Rich Web Clients Activity</a>
1.248 avankest 109: in the W3C <a href="http://www.w3.org/Interaction/">Interaction Domain</a>.</p>
1.12 avankest 110:
1.1 avankest 111: <p>This document was produced by a group operating under the
1.248 avankest 112: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004
113: W3C Patent Policy</a>. W3C maintains a
1.207 avankest 114: <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/42538/status">public
1.248 avankest 115: list of any patent disclosures</a> made in connection with the deliverables of
116: the group; that page also includes instructions for disclosing a patent. An
117: individual who has actual knowledge of a patent which the individual believes
118: contains
1.36 avankest 119: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
120: Claim(s)</a> must disclose the information in accordance with
121: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
122: 6 of the W3C Patent Policy</a>.</p>
1.12 avankest 123:
1.248 avankest 124: <p>Publication as a Working Draft does not imply endorsement by the W3C
125: Membership. This is a draft document and may be updated, replaced or
126: obsoleted by other documents at any time. It is inappropriate to cite this
127: document as other than work in progress.</p>
1.207 avankest 128:
129:
1.1 avankest 130: <h2 class="no-num no-toc" id="toc">Table of Contents</h2>
1.21 avankest 131:
1.1 avankest 132: <!--toc-->
1.12 avankest 133:
1.207 avankest 134:
135:
1.1 avankest 136: <h2 id="introduction">Introduction</h2>
1.12 avankest 137:
1.1 avankest 138: <p><em>This section is non-normative.</em></p>
1.12 avankest 139:
1.183 avankest 140: <p>The <code>XMLHttpRequest</code> object implements an interface exposed
141: by a scripting engine that allows scripts to perform HTTP client
142: functionality, such as submitting form data or loading data from a
143: server. It is the ECMAScript HTTP API.</p>
1.24 avankest 144:
1.1 avankest 145: <p>The name of the object is <code>XMLHttpRequest</code> for compatibility
1.183 avankest 146: with the Web, though each component of this name is potentially
147: misleading. First, the object supports any text based format, including
148: XML. Second, it can be used to make requests over both HTTP and HTTPS
149: (some implementations support protocols in addition to HTTP and HTTPS, but
150: that functionality is not covered by this specification). Finally, it
151: supports "requests" in a broad sense of the term as it pertains to HTTP;
152: namely all activity involved with HTTP requests or responses for the
153: defined HTTP methods.</p>
1.12 avankest 154:
1.14 avankest 155: <div class="example">
1.250 avankest 156: <p>Some simple code to do something with data from an XML document
157: fetched over the network:</p>
1.16 avankest 158:
1.58 avankest 159: <pre><code>function test(data) {
1.14 avankest 160: // taking care of data
161: }
162:
163: function handler() {
1.117 avankest 164: if(this.readyState == 4 && this.status == 200) {
1.14 avankest 165: // so far so good
1.117 avankest 166: if(this.responseXML != null && this.responseXML.getElementById('test').firstChild.data)
167: // success!
1.14 avankest 168: test(this.responseXML.getElementById('test').firstChild.data);
169: else
170: test(null);
1.117 avankest 171: } else if (this.readyState == 4 && this.status != 200) {
1.14 avankest 172: // fetched the wrong page or network error...
173: test(null);
174: }
175: }
1.12 avankest 176:
1.14 avankest 177: var client = new XMLHttpRequest();
178: client.onreadystatechange = handler;
1.250 avankest 179: client.open("GET", "unicorn.xml");
1.58 avankest 180: client.send();</code></pre>
1.16 avankest 181:
1.56 avankest 182: <p>If you just want to log a message to the server:</p>
1.16 avankest 183:
1.58 avankest 184: <pre><code>function log(message) {
1.14 avankest 185: var client = new XMLHttpRequest();
1.56 avankest 186: client.open("POST", "/log");
1.57 avankest 187: client.setRequestHeader("Content-Type", "text/plain;charset=UTF-8");
1.14 avankest 188: client.send(message);
1.58 avankest 189: }</code></pre>
1.16 avankest 190:
1.14 avankest 191: <p>Or if you want to check the status of a document on the server:</p>
1.16 avankest 192:
1.58 avankest 193: <pre><code>function fetchStatus(address) {
1.14 avankest 194: var client = new XMLHttpRequest();
195: client.onreadystatechange = function() {
196: // in case of network errors this might not give reliable results
197: if(this.readyState == 4)
198: returnStatus(this.status);
199: }
200: client.open("HEAD", address);
201: client.send();
1.58 avankest 202: }</code></pre>
1.14 avankest 203: </div>
1.12 avankest 204:
1.203 avankest 205:
206:
1.248 avankest 207:
208: <h2 id="conformance">Conformance Criteria</h2>
1.12 avankest 209:
1.27 avankest 210: <p>Everything in this specification is normative except for diagrams,
211: examples, notes and sections marked non-normative.</p>
1.12 avankest 212:
1.1 avankest 213: <p>The key words <em class="ct">must</em>, <em class="ct">must not</em>,
1.74 avankest 214: <em class="ct">should</em> and <em class="ct">may</em> in this document are
215: to be interpreted as described in RFC 2119.
216: [<cite><span>RFC2119</span></cite>]</p>
1.12 avankest 217:
1.1 avankest 218: <p>This specification defines the following classes of products:</p>
1.12 avankest 219:
1.1 avankest 220: <dl>
1.74 avankest 221: <dt><dfn id="conforming-user-agent">Conforming user agent</dfn></dt>
1.24 avankest 222:
1.74 avankest 223: <dd>
224: <p>A user agent <em class="ct">must</em> behave as described in this
1.106 avankest 225: specification in order to be considered conformant.</p>
1.95 avankest 226:
1.248 avankest 227:
1.224 avankest 228: <p>If the user agent is not a <span>conforming XML user agent</span> the
229: <span>XML response entity body</span> <em class="ct">must</em> (always)
1.239 avankest 230: be null.</p>
1.248 avankest 231:
1.140 avankest 232:
233: <p>User agents <em class="ct">may</em> implement algorithms given in
234: this specification in any way desired, so long as the end result is
235: indistinguishable from the result that would be obtained by the
236: specification's algorithms.</p>
1.110 avankest 237:
1.95 avankest 238: <p class="note">This specification uses both the terms "conforming user
239: agent(s)" and "user agent(s)" to refer to this product class.</p>
1.74 avankest 240: </dd>
1.248 avankest 241:
1.94 avankest 242: <dt><dfn id="conforming-xml-user-agent">Conforming XML user agent</dfn></dt>
1.110 avankest 243:
1.224 avankest 244: <dd><p>An XML user agent <em class="ct">must</em> be a
245: <span>conforming user agent</span> and <em class="ct">must</em> be a
246: conforming XML processor that reports violations of
247: namespace well-formedness. [<cite><span>XML</span></cite>]</p></dd>
1.248 avankest 248:
1.1 avankest 249: </dl>
1.32 avankest 250:
1.153 avankest 251: <h3 id="dependencies">Dependencies</h3>
1.33 avankest 252:
1.29 avankest 253: <p>This specification relies on several underlying specifications.</p>
1.248 avankest 254:
1.29 avankest 255: <dl>
1.248 avankest 256:
257:
1.29 avankest 258: <dt>DOM</dt>
1.33 avankest 259:
1.155 avankest 260: <dd><p>A <span title="conforming user agent">conforming user agent</span>
1.176 avankest 261: <em class="ct">must</em> support at least the subset of the functionality
1.182 avankest 262: defined in DOM Events and DOM Core that this specification relies upon,
263: such as various exceptions and <code>EventTarget</code>.
1.155 avankest 264: [<cite><span>DOM2Events</span></cite>]
265: [<cite><span>DOM3Core</span></cite>]</p></dd>
1.29 avankest 266:
1.250 avankest 267: <dt>HTML5</dt>
1.161 avankest 268:
269: <dd>
1.189 avankest 270: <p>A <span>conforming user agent</span> <em class="ct">must</em> support
1.250 avankest 271: at least the subset of the functionality defined in HTML5 that
1.197 avankest 272: this specification relies upon, such as the basics of the
273: <code>Window</code> object and serializing a <code>Document</code>
274: object. [<cite><span>HTML5</span></cite>]</p>
1.161 avankest 275:
276: <p class="note">The
277: <a href="http://www.w3.org/TR/2006/WD-Window-20060407/">Window Object
278: 1.0</a> draft is not referenced normatively as it appears to be no
1.250 avankest 279: longer maintained and HTML5 defines the <code>Window</code> object in
280: more detail. This specification already depends on HTML5 for other
281: reasons so there is not much additional overhead because of this.</p>
1.161 avankest 282:
1.29 avankest 283: <dt>HTTP</dt>
1.33 avankest 284:
1.248 avankest 285: <dd><p>A <span title="conforming user agent">conforming user agent</span>
286: <em class="ct">must</em> support some version of the HTTP protocol.
287: Requirements regarding HTTP are made throughout the specification.
288: [<cite><span>RFC2616</span></cite>]</p></dd>
1.189 avankest 289:
1.181 avankest 290: <dt>Web IDL</dt>
1.203 avankest 291:
1.248 avankest 292: <dd><p>A <span>conforming user agent</span> <em class="ct">must</em> also
293: be a conforming implementation of the IDL fragments in this
294: specification, as described in the Web IDL specification.
1.181 avankest 295: [<cite><span>WebIDL</span></cite>]
1.248 avankest 296:
297:
1.29 avankest 298: </dl>
1.12 avankest 299:
1.157 avankest 300:
1.153 avankest 301: <h3 id="terminology">Terminology</h3>
1.209 avankest 302:
303: <p>Comparing two strings in a
304: <dfn id="case-sensitive">case-sensitive</dfn> manner means comparing them
305: exactly, codepoint for codepoint.</p>
306:
307: <p>Comparing two strings in an
308: <dfn id="ascii-case-insensitive">ASCII case-insensitive</dfn> manner means
309: comparing them exactly, codepoint for codepoint, except that the
310: characters in the range U+0041 .. U+005A (i.e. LATIN CAPITAL LETTER A to
311: LATIN CAPITAL LETTER Z) and the corresponding characters in the range
312: U+0061 .. U+007A (i.e. LATIN SMALL LETTER A to LATIN SMALL LETTER Z) are
313: considered to also match.</p>
314:
315: <p><dfn id="converted-to-ascii-upercase" title="converted to ASCII uppercase">Converting a string to ASCII uppercase</dfn>
316: means replacing all characters in the range U+0061 .. U+007A (i.e.
317: LATIN SMALL LETTER A to LATIN SMALL LETTER Z) with the corresponding
318: characters in the range U+0041 .. U+005A (i.e. LATIN CAPITAL LETTER A to
319: LATIN CAPITAL LETTER Z).</p>
1.12 avankest 320:
1.233 avankest 321: <p><dfn id="dfn-obtain-unicode">convert a DOMString to a sequence of Unicode characters</dfn>
322: is defined by the Web IDL specification.
323: [<cite><span>WebIDL</span></cite>]</p>
1.248 avankest 324:
1.200 avankest 325: <p>The terms and algorithms
326: <dfn id="url-fragment"><fragment></dfn>,
327: <dfn id="url-scheme"><scheme></dfn>,
1.203 avankest 328: <dfn id="document-base-url">document base URL</dfn>,
1.244 avankest 329: <dfn id="document-character-encoding">document's character encoding</dfn>,
1.205 avankest 330: <dfn id="event-handler-attributes-0">event handler attributes</dfn>,
1.203 avankest 331: <dfn id="event-handler-event-type">event handler event type</dfn>,
332: <dfn id="fully-active">fully active</dfn>,
1.206 avankest 333: <dfn id="function"><code>Function</code></dfn>,
1.225 avankest 334: <dfn id="dom-innerhtml" title="dom-innerHTML"><code>innerHTML</code></dfn>,
1.200 avankest 335: <dfn id="origin">origin</dfn>,
1.232 avankest 336: <dfn id="preferred-mime-name">preferred MIME name</dfn>,
1.203 avankest 337: <dfn id="resolve-a-url">resolve a URL</dfn>,
338: <dfn id="same-origin">same origin</dfn>,
339: <dfn id="storage-mutex">storage mutex</dfn>,
340: <dfn id="task">task</dfn>,
341: <dfn id="task-source">task source</dfn>,
1.252 ! avankest 342: <dfn id="task-queues">task queues</dfn>,
1.203 avankest 343: <dfn id="url">URL</dfn>,
1.232 avankest 344: <dfn id="url-character-encoding">URL character encoding</dfn>,
345: <dfn id="queue-a-task">queue a task</dfn>, and
346: <dfn id="valid-mime-type">valid MIME type</dfn>
1.250 avankest 347: are defined by the HTML5 specification.
1.157 avankest 348: [<cite><span>HTML5</span></cite>]</p>
1.210 avankest 349:
1.203 avankest 350: <p>The term <dfn id="entity-body">entity body</dfn> is used as described
351: in RFC 2616. <dfn id="method-token">Method token</dfn> is used as
352: described in section 5.1.1 of RFC 2616. <dfn><code>field-name</code></dfn>
353: and <dfn><code>field-value</code></dfn> are used as described in section
354: 4.2 of RFC 2616. [<cite><span>RFC2616</span></cite>]</p>
1.218 avankest 355:
1.203 avankest 356: <p><dfn><code>userinfo</code></dfn> is used as described in section 3.2.1
357: of RFC 3986. [<cite><span>RFC3986</span></cite>]</p>
358:
359: <p>To <dfn id="dispatch-readystatechange-event">dispatch a
360: <code>readystatechange</code> event</dfn> means that an event with the
1.232 avankest 361: name <code>readystatechange</code>, which does not bubble and is not
362: cancelable, and which uses the <code>Event</code> interface, is to be
363: dispatched at the <code>XMLHttpRequest</code> object.</p>
1.80 avankest 364:
1.248 avankest 365:
366:
1.153 avankest 367: <h3 id="extensibility">Extensibility</h3>
1.12 avankest 368:
1.250 avankest 369: <p>User agents, Working Groups, and other interested parties are
370: <em>strongly encouraged</em> to discuss extensions on a relevant public
371: forum, preferably
372: <a href="mailto:public-webapps@w3.org">public-webapps@w3.org</a>. If this
373: is for some reason not possible prefix the extension in some way and start
374: the prefix with an uppercase letter. E.g. if company Foo wants to add a
375: private method <code>bar()</code> it could be named <code>FooBar()</code>
376: to prevent clashes with a potential future standardized
377: <code>bar()</code>.</p>
1.12 avankest 378:
1.153 avankest 379:
1.223 avankest 380: <h2>The <code title="">XMLHttpRequest</code> Interface</h2>
1.12 avankest 381:
1.58 avankest 382: <p>The <code>XMLHttpRequest</code> object can be used by scripts to
1.22 avankest 383: programmatically connect to their originating server via HTTP.</p>
1.12 avankest 384:
1.228 avankest 385: <pre class="idl">[NoInterfaceObject]
386: interface <dfn id="xmlhttprequesteventtarget">XMLHttpRequestEventTarget</dfn> : EventTarget {
387: // for future use
388: };
389:
1.240 avankest 390: [<span title="dom-XMLHttpRequest">Constructor</span>]
1.228 avankest 391: interface <dfn id="xmlhttprequest">XMLHttpRequest</dfn> : <span>XMLHttpRequestEventTarget</span> {
1.206 avankest 392: // <a href="#event-handler-attributes">event handler attributes</a>
393: attribute <span>Function</span> <span>onreadystatechange</span>;
1.58 avankest 394:
1.205 avankest 395: // <a href="#states">states</a>
1.71 avankest 396: const unsigned short <span title="UNSENT state">UNSENT</span> = 0;
1.134 avankest 397: const unsigned short <span title="OPENED state">OPENED</span> = 1;
1.123 avankest 398: const unsigned short <span title="HEADERS_RECEIVED state">HEADERS_RECEIVED</span> = 2;
1.86 avankest 399: const unsigned short <span title="LOADING state">LOADING</span> = 3;
1.117 avankest 400: const unsigned short <span title="DONE state">DONE</span> = 4;
1.70 avankest 401: readonly attribute unsigned short <span>readyState</span>;
1.58 avankest 402:
1.205 avankest 403: // <a href="#request">request</a>
1.226 avankest 404: void <span>open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>);
405: void <span>open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>, boolean <var>async</var>);
1.228 avankest 406: void <span>open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>, boolean <var>async</var>, DOMString? <var>user</var>);
407: void <span>open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>, boolean <var>async</var>, DOMString? <var>user</var>, DOMString? <var>password</var>);
1.226 avankest 408: void <span>setRequestHeader</span>(DOMString <var>header</var>, DOMString <var>value</var>);
1.70 avankest 409: void <span>send</span>();
1.226 avankest 410: void <span>send</span>(Document <var>data</var>);
1.228 avankest 411: void <span>send</span>([AllowAny] DOMString? <var>data</var>);
1.70 avankest 412: void <span>abort</span>();
1.58 avankest 413:
1.205 avankest 414: // <a href="#response">response</a>
1.203 avankest 415: readonly attribute unsigned short <span>status</span>;
416: readonly attribute DOMString <span>statusText</span>;
1.226 avankest 417: DOMString <span>getResponseHeader</span>(DOMString <var>header</var>);
1.70 avankest 418: DOMString <span>getAllResponseHeaders</span>();
419: readonly attribute DOMString <span>responseText</span>;
420: readonly attribute Document <span>responseXML</span>;
1.228 avankest 421: };</pre>
1.8 avankest 422:
1.235 avankest 423: <!-- XXX domintro boxes; HTML5-style -->
424:
1.124 avankest 425:
1.203 avankest 426: <h3>Origin and Base URL</h3>
427:
428: <p>Each <code>XMLHttpRequest</code> object has an associated
429: <dfn id="xmlhttprequest-origin"><code>XMLHttpRequest</code> origin</dfn>
430: and an
431: <dfn id="xmlhttprequest-base-url"><code>XMLHttpRequest</code> base URL</dfn>.
432:
433: <p>This specification defines their values when the global object is
434: represented by the <code>Window</code> object. When the
1.246 avankest 435: <code>XMLHttpRequest</code> object is used in other contexts their values
1.203 avankest 436: will have to be defined as appropriate for that context. That is
437: considered to be out of scope for this specification.</p>
438:
439: <hr>
440:
441: <p>In environments where the global object is represented by the
442: <code>Window</code> object the <code>XMLHttpRequest</code> object has an
443: associated
444: <dfn id="xmlhttprequest-document"><code>XMLHttpRequest</code> <code>Document</code></dfn>
445: which is the <code>Document</code> object associated with the
446: <code>Window</code> object for which the <code>XMLHttpRequest</code>
447: interface object was created.</p>
448:
449: <p class="note">The
450: <span><code>XMLHttpRequest</code> <code>Document</code></span> is used to
451: determine the <span><code>XMLHttpRequest</code> origin</span> and
452: <span><code>XMLHttpRequest</code> base URL</span> at a later stage.</p>
453:
454:
455: <h3>Task Sources</h3>
1.218 avankest 456:
1.251 avankest 457: <p>The <span>task source</span> used by this specification is the
458: <dfn><code>XMLHttpRequest</code> task source</dfn>.</p>
1.203 avankest 459:
460:
1.211 avankest 461: <h3 id="constructors">Constructors</h3>
1.203 avankest 462:
463: <p>When the
1.240 avankest 464: <dfn id="dom-xmlhttprequest" title="dom-XMLHttpRequest"><code title="">XMLHttpRequest()</code></dfn>
1.203 avankest 465: constructor is invoked, the user agent <em class="ct">must</em> return a
466: new <code>XMLHttpRequest</code> object.</p>
467:
468:
1.205 avankest 469: <h3 id="event-handler-attributes">Event Handler Attributes</h3>
470:
1.248 avankest 471:
472:
1.205 avankest 473: <p>The following is the
474: <span title="event handler attributes">event handler attribute</span> (and
475: its corresponding <span>event handler event type</span>) that
476: <em class="ct">must</em> be supported as DOM attribute by the
477: <code>XMLHttpRequest</code> object:</p>
478:
479: <table>
480: <thead>
481: <tr>
482: <th><span title="event handler attributes">event handler attribute</span>
483: <th><span>event handler event type</span>
484: <tbody>
485: <tr>
486: <td><dfn id="onreadystatechange"><code>onreadystatechange</code></dfn>
487: <td><code>readystatechange</code></td>
488: </table>
489:
490:
491: <h3 id="states">States</h3>
1.203 avankest 492:
493: <p>The <code>XMLHttpRequest</code> object can be in several states. The
494: <dfn id="readystate"><code>readyState</code></dfn> attribute, on getting,
495: <em class="ct">must</em> return the current state, which
496: <em class="ct">must</em> be one of the following values:</p>
497:
498: <dl>
499: <dt><dfn id="unsent-state" title="UNSENT state"><code>UNSENT</code></dfn>
500: (numeric value 0)</dt>
501: <dd><p>The object has been constructed.</p></dd>
502:
503: <dt><dfn id="opened-state" title="OPENED state"><code>OPENED</code></dfn>
504: (numeric value 1)</dt>
505: <dd><p>The <code>open()</code> method has been successfully invoked.
506: During this state request headers can be set using
507: <code>setRequestHeader()</code> and the request can be made using the
508: <code>send()</code> method.</p></dd>
509:
510: <dt><dfn id="headers-received-state" title="HEADERS_RECEIVED state"><code>HEADERS_RECEIVED</code></dfn>
511: (numeric value 2)</dt>
512: <dd><p>All HTTP headers have been received. Several response members of
513: the object are now available.</p></dd>
514:
515: <dt><dfn id="loading-state" title="LOADING state"><code>LOADING</code></dfn>
516: (numeric value 3)</dt>
517: <dd><p>The <span>response entity body</span> is being received.</p></dd>
518:
519: <dt><dfn id="done-state" title="DONE state"><code>DONE</code></dfn>
520: (numeric value 4)</dt>
521: <dd><p>The data transfer has been completed or something went wrong
522: during the transfer (e.g. infinite redirects).</p></dd>
523: </dl>
524:
525: <p>The <span title="OPENED state">OPENED</span> state has an associated
526: <dfn id="send-flag"><code>send()</code> flag</dfn> that indicates whether
527: the <code>send()</code> method has been invoked. It can be either true
528: or false and has an initial value of false.</p>
529:
530: <p>The <span title="DONE state">DONE</span> state has an associated
531: <dfn id="error-flag">error flag</dfn> that indicates some type of network
532: error or abortion. It can be either true or false and has an initial value
533: of false.</p>
534:
535:
1.205 avankest 536: <h3 id="request">Request</h3>
1.203 avankest 537:
538: <p>The <code>XMLHttpRequest</code> object holds the following request
539: metadata variables:</p>
540:
1.204 avankest 541: <dl>
542: <dt>The <dfn>asynchronous flag</dfn></dt>
543: <dd>A flag that is either true or false that indicates whether the
544: request is done asynchronously.</dd>
545:
546: <dt>The <dfn>request method</dfn></dt>
547: <dd>The method used in the request.</dd>
548:
549: <dt>The <dfn>request URL</dfn></dt>
550: <dd>The <span>URL</span> used in the request.</dd>
1.218 avankest 551:
1.204 avankest 552: <dt>The <dfn>request username</dfn></dt>
553: <dd>The username used in the request or null if there is no
554: username.</dd>
1.218 avankest 555:
1.204 avankest 556: <dt>The <dfn>request password</dfn></dt>
557: <dd>The password used in the request or null if there is no
558: password.</dd>
1.218 avankest 559:
1.204 avankest 560: <dt>The <dfn id="author-request-headers">author request headers</dfn></dt>
561: <dd>A list consisting of HTTP header name/value pairs to be used in the
562: request.</p>
1.203 avankest 563:
1.204 avankest 564: <dt>The <dfn>request entity body</dfn></dt>
1.218 avankest 565: <dd>The <span>entity body</span> used in the request.</dd>
1.248 avankest 566:
567:
1.204 avankest 568: </dl>
1.203 avankest 569:
1.248 avankest 570:
571:
1.203 avankest 572:
573: <h4>The <code title="">open()</code> method</h4>
1.88 avankest 574:
1.203 avankest 575: <p>When the <dfn id="open" title="open"><code>open(<var>method</var>,
576: <var title="">url</var>, <var>async</var>, <var>user</var>,
577: <var>password</var>)</code></dfn> method is invoked, the user agent
1.217 avankest 578: <em class="ct">must</em> run these steps (unless otherwise indicated):</p>
1.90 avankest 579:
1.88 avankest 580: <ol>
1.203 avankest 581: <li>
582: <p>If the <code>XMLHttpRequest</code> object has an associated
583: <span><code>XMLHttpRequest</code> <code>Document</code></span> run
584: these substeps:</p>
1.90 avankest 585:
1.203 avankest 586: <ol>
587: <li><p>If the
588: <span><code>XMLHttpRequest</code> <code>Document</code></span> is not
589: <span>fully active</span> raise an <code>INVALID_STATE_ERR</code>
590: exception and terminate the overall set of steps.</p></li>
591:
592: <li><p>Let <span><code>XMLHttpRequest</code> base URL</span> be the
593: <span>document base URL</span> of the
594: <span><code>XMLHttpRequest</code> <code>Document</code></span>.</p></li>
595:
596: <li><p>Let <span><code>XMLHttpRequest</code> origin</span> be the
597: <span>origin</span> of the
598: <span><code>XMLHttpRequest</code> <code>Document</code></span>.</p></li>
599: </ol>
600: </li>
1.90 avankest 601:
1.203 avankest 602: <li><p>If <var>method</var> does not match the
1.210 avankest 603: <span>Method token</span> production raise a <code>SYNTAX_ERR</code>
604: exception and terminate these steps.</p></li>
1.118 avankest 605:
1.115 avankest 606: <li>
1.203 avankest 607: <p>If <var>method</var> is an
608: <span>ASCII case-insensitive</span> match for
609: <code>CONNECT</code>, <code>DELETE</code>, <code>GET</code>,
610: <code>HEAD</code>, <code>OPTIONS</code>, <code>POST</code>,
611: <code>PUT</code>, <code>TRACE</code>, or <code>TRACK</code>
1.209 avankest 612: <span title="converted to ASCII uppercase">convert <var>method</var> to ASCII uppercase</span>.</p>
1.118 avankest 613:
1.203 avankest 614: <p class="note">If it does not match any of the above, it is passed
615: through <em>literally</em>, including in the final request.</p>
1.115 avankest 616: </li>
1.203 avankest 617: <!-- WebKit (and supposedly Gecko) also uppercase: COPY, INDEX, LOCK,
618: M-POST, MKCOL, MOVE, PROPFIND, PROPPATCH, and UNLOCK. -->
1.118 avankest 619:
1.111 avankest 620: <li>
1.209 avankest 621: <p>If <var>method</var> is a <span>case-sensitive</span> match for
622: <code>CONNECT</code>, <code>TRACE</code>, or <code>TRACK</code> the
623: user agent <em class="ct">should</em> raise a <code>SECURITY_ERR</code>
624: exception and terminate these steps.</p>
1.117 avankest 625:
1.203 avankest 626: <p class="note">Allowing these methods poses a security risk.
627: [<cite><span>HTTPVERBSEC</span></cite>]</p>
1.111 avankest 628: </li>
629:
1.203 avankest 630: <li><p>Let <var title="">url</var> be a <span>URL</span>.</p></li>
631:
1.209 avankest 632: <li><p>Let <span>URL character encoding</span> of <var title="">url</var>
633: be UTF-8.</p></li>
1.113 avankest 634:
1.203 avankest 635: <li><p><span title="Resolve a URL">Resolve <var title="">url</var></span>
636: relative to the <span><code>XMLHttpRequest</code> base URL</span>.
637: If the algorithm returns an error raise a <code>SYNTAX_ERR</code>
638: exception and terminate these steps.</p></li>
639:
640: <!-- Presto and Gecko override the encoding. WebKit does not. Trident
641: does not support non-ASCII URLs. This matters for the <query> component,
642: see HTML5. -->
643:
644: <li><p>Drop <code><fragment></code> from <var title="">url</var>.</p></li>
645:
646: <li><p>If <var title="">url</var> contains an unsupported <code><scheme></code>
647: raise a <code>NOT_SUPPORTED_ERR</code> and terminate these
648: steps.</p></li>
649:
650: <li><p>If the <code>"user:password"</code> format in the
651: <code>userinfo</code> production is not supported for the relevant scheme
652: and <var title="">url</var> contains this format raise a
653: <code>SYNTAX_ERR</code> and terminate these steps.</p></li>
654:
655: <li><p>If <var title="">url</var> contains the <code>"user:password"</code>
656: format let <var>temp user</var> be the user part and
657: <var>temp password</var> be the password part.</p></li>
658:
659: <li><p>If <var title="">url</var> just contains the <code>"user"</code>
660: format let <var>temp user</var> be the user part.</p></li>
661:
1.248 avankest 662:
1.203 avankest 663: <li><p>If the <span>origin</span> of <var title="">url</var> is not
664: <span>same origin</span> with the
665: <span><code>XMLHttpRequest</code> origin</span> the user agent
666: <em class="ct">should</em> raise a <code>SECURITY_ERR</code> exception
667: and terminate these steps.</p></li>
1.248 avankest 668:
669:
1.203 avankest 670:
1.211 avankest 671: <li><p>Let <var>async</var> be the value of the <var>async</var> argument
672: or <code>true</code> if it was omitted.</p></li>
1.203 avankest 673:
674: <li>
675: <p>If the <var>user</var> argument was not omitted follow these sub
676: steps:</p>
1.90 avankest 677:
1.203 avankest 678: <ol>
679: <li><p>If the syntax of <var>user</var> does not match the syntax
680: specified by the relevant authentication scheme, raise a
681: <code>SYNTAX_ERR</code> exception and terminate the overall set of
682: steps.</p></li>
1.163 avankest 683:
1.239 avankest 684: <li><p>If <var>user</var> is null let <var>temp user</var>
1.203 avankest 685: be null.</p></li>
1.90 avankest 686:
1.203 avankest 687: <li><p>Otherwise let <var>temp user</var> be <var>user</var>.</p></li>
688: </ol>
1.88 avankest 689:
1.203 avankest 690: <p class="note">These steps override anything that may have been set by
691: the <var title="">url</var> argument.</p>
692: </li>
1.88 avankest 693:
1.128 avankest 694: <li>
1.203 avankest 695: <p>If the <var>password</var> argument was not omitted follow these sub
696: steps:</p>
697:
698: <ol>
699: <li><p>If the syntax of <var>password</var> does not match the syntax
700: specified by the relevant authentication scheme, raise a
701: <code>SYNTAX_ERR</code> exception and terminate the overall set of
702: steps.</p></li>
1.167 avankest 703:
1.239 avankest 704: <li><p>If <var>password</var> is null let
1.203 avankest 705: <var>temp password</var> be null.</p></li>
706:
707: <li><p>Otherwise let <var>temp password</var> be
708: <var>password</var>.</p></li>
709: </ol>
710:
711: <p class="note">These steps override anything that may have been set by
712: the <var title="">url</var> argument.</p>
1.128 avankest 713: </li>
1.88 avankest 714:
1.203 avankest 715: <li><p><span title="abort send()">Abort the <code>send()</code> algorithm</span>.</p></li>
716:
717: <li><p>The user agent <em class="ct">should</em> cancel any network
718: activity for which the object is responsible.</p></li>
719: <!-- we can hardly require it... -->
720:
1.252 ! avankest 721: <li><p>If there are any <span title="task">tasks</span> from the object's
! 722: <span><code>XMLHttpRequest</code> task source</span> in one of the
! 723: <span>task queues</span>, then remove those tasks.</p></li>
! 724:
1.203 avankest 725: <li>
726: <p>Set variables associated with the object as follows:</p>
727:
728: <ul>
729: <li><p>Set the <span><code>send()</code> flag</span> to false.</p></li>
730:
731: <li><p>Set <span>response entity body</span> to null.</p></li>
732:
733: <li><p>Empty the list of <span>author request headers</span>.</p>
734:
735: <li><p>Set the <span>request method</span> to <var>method</var>.</p></li>
736:
737: <li><p>Set the <span>request URL</span> to <var title="">url</var>.</p></li>
1.58 avankest 738:
1.203 avankest 739: <li><p>Set the <span>request username</span> to <var>temp user</var>.</p></li>
1.12 avankest 740:
1.203 avankest 741: <li><p>Set the <span>request password</span> to <var>temp password</var>.</p></li>
1.12 avankest 742:
1.203 avankest 743: <li><p>Set the <span>asynchronous flag</span> to true if <var>async</var> is
744: <code>true</code>. Otherwise set it to false.</p></li>
745: </ul>
746: </li>
1.58 avankest 747:
1.203 avankest 748: <li><p>Switch the the state to
749: <span title="OPENED state">OPENED</span>.</p></li>
1.58 avankest 750:
1.203 avankest 751: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
752: </ol>
1.248 avankest 753:
754:
1.203 avankest 755: <p class="note">A future version or extension of this specification will
756: define a way of doing cross-origin requests.</p>
1.248 avankest 757:
1.58 avankest 758:
1.14 avankest 759:
1.203 avankest 760: <h4>The <code title="">setRequestHeader()</code> method</h4>
1.12 avankest 761:
1.235 avankest 762: <!-- XXX domintro authors
1.203 avankest 763: The <code>setRequestHeader()</code> method can be used to set new request
1.184 avankest 764: headers and append to request headers already in the list.</p>
1.203 avankest 765: -->
1.45 avankest 766:
1.203 avankest 767: <p>As indicated in the algorithm below certain headers cannot be set and
768: are left up to the user agent. In addition there are certain other headers
769: the user agent will take control of if they are not set by the author as
770: indicated at the end of the <code>send()</code> method section.</p>
771:
772: <p class="note">The <code>setRequestHeader()</code> method appends a
773: value if the HTTP header given as argument is already part of the
774: <span>author request headers</span> list.</p>
775:
1.248 avankest 776:
777:
1.203 avankest 778: <p>When the
779: <dfn id="setrequestheader" title="setrequestheader"><code>setRequestHeader(<var>header</var>,
780: <var>value</var>)</code></dfn> method is invoked, the user agent
1.217 avankest 781: <em class="ct">must</em> run these steps (unless otherwise indicated):</p>
1.14 avankest 782:
1.203 avankest 783: <ol>
784: <li><p>If the state is not <span title="OPENED state">OPENED</span> raise
785: an <code>INVALID_STATE_ERR</code> exception and terminate these
786: steps.</p></li>
787:
788: <li><p>If the <span><code>send()</code> flag</span> is true raise an
789: <code>INVALID_STATE_ERR</code> exception and terminate these
790: steps.</p></li>
791:
792: <li><p>If <var>header</var> does not match the <code>field-name</code>
793: production raise a <code>SYNTAX_ERR</code> exception and terminate these
794: steps.</p></li>
795:
796: <li>
797: <p>If the <var>value</var> argument does not match the
798: <code>field-value</code> production raise a <code>SYNTAX_ERR</code> and
799: terminate these steps.</p>
800:
801: <p class="note">The empty string is legal and represents the empty
802: header value.</p>
803: </li>
804:
805: <li>
806: <p>For security reasons, these steps <em class="ct">should</em> be
807: terminated if <var>header</var> is an
808: <span>ASCII case-insensitive</span> match for one of the following
809: headers:</p>
810:
811: <ul>
812: <li><code>Accept-Charset</code></li>
813: <li><code>Accept-Encoding</code></li>
814: <li><code>Connection</code></li>
815: <li><code>Content-Length</code></li>
816: <li><code>Cookie</code></li>
817: <li><code>Cookie2</code></li>
818: <li><code>Content-Transfer-Encoding</code></li>
819: <li><code>Date</code></li>
820: <li><code>Expect</code></li>
821: <li><code>Host</code></li>
822: <li><code>Keep-Alive</code></li>
823: <li><code>Referer</code></li>
824: <li><code>TE</code></li>
825: <li><code>Trailer</code></li>
826: <li><code>Transfer-Encoding</code></li>
827: <li><code>Upgrade</code></li>
828: <li><code>User-Agent</code></li>
829: <li><code>Via</code></li>
830: </ul>
1.96 avankest 831:
1.203 avankest 832: <p>… or if the start of <var>header</var> is an
833: <span>ASCII case-insensitive</span> match for <code>Proxy-</code> or
834: <code>Sec-</code> (including when <var>header</var> is just
835: <code>Proxy-</code> or <code>Sec-</code>).</p>
836:
837: <p class="note">The above headers are not allowed to be set as they are
838: better controlled by the user agent as it knows best what value they
839: should have. Header names starting with <code>Sec-</code> are not
840: allowed to be set to allow new headers to be minted in the future that
841: are guaranteed not to come from <code>XMLHttpRequest</code>. (Older
842: clients would however still be vulnerable as they allow such headers to
843: be set.)</p>
844: </li>
1.14 avankest 845:
1.203 avankest 846: <li><p>If <var>header</var> is not in the
847: <span>author request headers</span> list append <var>header</var> with
848: its associated <var>value</var> to the list and terminate these
849: steps.</p></li>
850:
851: <li><p>If <var>header</var> is in the <span>author request headers</span>
852: list either use multiple headers, combine the values or use a combination
853: of those (section 4.2, RFC 2616).
854: [<cite><span>RFC2616</span></cite>]</p></li>
855: <!-- XXX it seems UAs always combine the values -->
856: </ol>
1.45 avankest 857:
1.203 avankest 858: <p class="note">See also the <code>send()</code> method regarding user
859: agent header handling for caching, authentication, proxies, and
860: cookies.</p>
1.14 avankest 861:
1.203 avankest 862: <div class="example">
863: <pre><code>// The following script:
1.14 avankest 864: var client = new XMLHttpRequest();
865: client.open('GET', 'demo.cgi');
866: client.setRequestHeader('X-Test', 'one');
867: client.setRequestHeader('X-Test', 'two');
868: client.send();
869:
870: // ...would result in the following header being sent:
871: ...
872: X-Test: one, two
1.58 avankest 873: ...</code></pre>
1.203 avankest 874: </div>
1.248 avankest 875:
876:
1.218 avankest 877:
1.203 avankest 878:
879: <h4>The <code title="">send()</code> method</h4>
1.12 avankest 880:
1.235 avankest 881: <!-- XXX domintro
1.203 avankest 882: <p>The <code>send()</code> method initiates the request and its optional
1.204 avankest 883: argument provides the <span>request entity body</span>.</p>
1.235 avankest 884: -->
1.203 avankest 885:
886: <p>When the
887: <dfn id="send" title="send"><code>send(<var>data</var>)</code></dfn>
888: method is invoked, the user agent <em class="ct">must</em> run the
889: following steps (unless otherwise noted). This algorithm gets aborted when
890: the <code>open()</code> or <code>abort()</code> method is invoked. When
891: the
892: <dfn title="abort send()" id="abort-send-algorithm"><code>send()</code> algorithm is aborted</dfn>
893: the user agent <em class="ct">must</em> terminate the algorithm after
894: finishing the step it is on.</p>
895:
896: <p class="note">The <code title="">send()</code> algorithm can only be
897: aborted when the <span>asynchronous flag</span> is true and only after the
898: method call has returned.</p>
1.181 avankest 899:
1.203 avankest 900: <ol>
901: <li><p>If the state is not <span title="OPENED state">OPENED</span> raise
902: an <code>INVALID_STATE_ERR</code> exception and terminate these
903: steps.</p></li>
904:
905: <li><p>If the <span><code>send()</code> flag</span> is true raise an
906: <code>INVALID_STATE_ERR</code> exception and terminate these
907: steps.</p></li>
1.58 avankest 908:
1.203 avankest 909: <li>
910: <p>If the <span>request method</var> is <code>GET</code> or
1.239 avankest 911: <code>HEAD</code> act as if <var>data</var> is null.</p>
1.232 avankest 912:
913: <p>If the <var>data</var> argument has been omitted or is
1.239 avankest 914: null, do not include a <span>request entity body</span>
1.232 avankest 915: and go to the next step.</p>
1.248 avankest 916:
917: <p>Otherwise, let <var>encoding</var> be null, <var>mime type</var> be
918: null, and then follow these rules:</p>
1.203 avankest 919:
920: <dl class="switch">
1.248 avankest 921:
922:
923: <dt>If <var>data</var> is a <code>Document</code>
1.203 avankest 924:
925: <dd>
1.232 avankest 926: <p>Let <var>encoding</var> be the <span>preferred MIME name</span> of
927: the
928: <span title="document's character encoding">character encoding</span>
929: of <var>data</var>. If <var>encoding</var> is UTF-16 change it to
930: UTF-8.</p>
931:
1.248 avankest 932: <p>Let <var>mime type</var> be "<code>application/xml;charset=</code>"
933: followed by <var>encoding</var>.</p>
1.232 avankest 934:
935: <p>Let the <span>request entity body</span> be the result of getting
936: the <code title="dom-innerHTML">innerHTML</code> attribute on
1.233 avankest 937: <var>data</var>
938: <span title="convert a DOMString to a sequence of Unicode characters">converted to Unicode</span>
939: and encoded as <var>encoding</var>. Re-raise any exception this
940: raises.</p>
1.218 avankest 941:
1.233 avankest 942: <p class="note">In particular, if the document cannot be serialized an
1.217 avankest 943: <code>INVALID_STATE_ERR</code> exception is raised.</p>
944:
1.203 avankest 945: <p class="note">Subsequent changes to the <code>Document</code> have
946: no effect on what is submitted.</p>
947: </dd>
1.237 avankest 948:
1.248 avankest 949: <dt>If <var>data</var> is a <code>DOMString</code></dt>
1.237 avankest 950:
1.248 avankest 951: <dd>
952: <p>Let <var>encoding</var> be UTF-8.</p>
953:
954: <p>Let <var>mime type</var> be "<code>text/plain;charset=UTF-8</code>".</p>
955:
956: <p>Let the <span>request entity body</span> be <var>data</var>
957: <span title="convert a DOMString to a sequence of Unicode characters">converted to Unicode</span>
958: and encoded as UTF-8.</p>
959: </dd>
960:
961:
1.203 avankest 962: </dl>
1.58 avankest 963:
1.232 avankest 964: <p>If a <code>Content-Type</code> header is set using
1.248 avankest 965: <code>setRequestHeader()</code> whose value is a
966: <span>valid MIME type</span> and has a <code>charset</code>
1.232 avankest 967: parameter whose value is not an <span>ASCII case-insensitive</span>
1.248 avankest 968: match for <var>encoding</var>, and <var>encoding</var> is not null, set
969: all the <code>charset</code> parameters of the
970: <code>Content-Type</code> header to <var>encoding</var>.</p>
1.232 avankest 971:
972: <p>If no <code>Content-Type</code> header has been set using
1.248 avankest 973: <code>setRequestHeader()</code> and <var>mime type</var> is not null set
974: a <code>Content-Type</code> request header with as value
975: <var>mime type</var>.</p>
1.236 avankest 976:
977: <!-- reminder: if we ever change this to always include charset it has
978: to be included as the first parameter for compatibility reasons -->
1.203 avankest 979: </li>
1.202 avankest 980:
1.203 avankest 981: <li><p>If the <span>asynchronous flag</span> is false release the
982: <span>storage mutex</span>.</p></li>
1.103 avankest 983:
1.248 avankest 984:
985:
1.203 avankest 986: <li><p>Set the <span>error flag</span> to false.</p></li>
1.218 avankest 987:
1.248 avankest 988:
989:
1.211 avankest 990: <li>
991: <p>If the <span>asynchronous flag</span> is true run these substeps:</p>
1.218 avankest 992:
1.211 avankest 993: <ol>
1.217 avankest 994: <li><p>Set the <span><code>send()</code> flag</span> to true.</p></li>
995:
1.211 avankest 996: <li>
997: <p><span>Dispatch a <code>readystatechange</code> event</span>.</p>
1.145 avankest 998:
1.211 avankest 999: <p class="note">The state does not change. The event is dispatched for
1000: historical reasons.</p>
1001: </li>
1002:
1.248 avankest 1003:
1004:
1.211 avankest 1005: <li><p>Return the <code>send()</code> method call, but continue running
1006: the steps in this algorithm.</p></li>
1007: </ol>
1008: </li>
1.218 avankest 1009:
1.203 avankest 1010: <li>
1.248 avankest 1011:
1.211 avankest 1012:
1.248 avankest 1013: <p>Make a request to <span>request URL</span>, using HTTP method
1014: <span>request method</span>, user <span>request username</span> (if
1015: non-null) and password <span>request password</span> (if non-null),
1016: taking into account the <span>request entity body</span>, list of
1017: <span>author request headers</span> and the rules listed at the end of
1018: this section.</p>
1019:
1020: <p>If there are cookies to be set, run the
1021: <span>cookie steps</span>.</p>
1022:
1023: <dl class="switch">
1024: <dt>If the <span>asynchronous flag</span> is false</dt>
1025: <dd>
1026: <p>While making the request also follow the
1027: <span>same-origin request event rules</span>.</p>
1028:
1029: <!--
1030: This cannot involve any task queue whatsoever because that would
1031: mean other tasks on the task queue might get processed as well
1032: which is counter to the whole idea of doing things synchronous.
1033: -->
1034:
1035: <p class="note">The <code>send()</code> method call will now be
1036: returned by virtue of this algorithm ending.</p>
1037: </dd>
1038:
1039: <dt>If the <span>asynchronous flag</span> is true</dt>
1040: <dd>
1041: <p><span>Make progress notifications</span>.</p>
1042:
1043: <p><span>Make upload progress notifications</span>.</p>
1044:
1045: <p>While processing the request, as data becomes available and when
1046: the user interferes with the request,
1047: <span title="queue a task">queue tasks</span> to follow the
1.251 avankest 1048: <span>same-origin request event rules</span>.</p>
1.248 avankest 1049: </dd>
1050: </dl>
1051:
1.203 avankest 1052: </li>
1053: </ol>
1.60 avankest 1054:
1.203 avankest 1055: <hr>
1056:
1.227 avankest 1057: <p>If the user agent allows the end user to configure a proxy it
1.248 avankest 1058: <em class="ct">should</em> modify the request appropriately; i.e., connect
1059: to the proxy host instead of the origin server, modify the
1060: <code>Request-Line</code> and send <code>Proxy-Authorization</code>
1061: headers as specified.</p>
1.212 avankest 1062:
1.218 avankest 1063: <p>If the user agent supports HTTP Authentication and
1064: <code>Authorization</code> is not in the list of
1065: <span>author request headers</span>, it <em class="ct">should</em>
1066: consider requests originating from the <code>XMLHttpRequest</code> object
1067: to be part of the protection space that includes the accessed URIs and
1068: send <code>Authorization</code> headers and handle
1069: <code>401 Unauthorized</code> requests appropriately. If authentication
1.247 avankest 1070: fails, and <span>request username</span> and <span>request password</span>
1.227 avankest 1071: are both null, user agents <em class="ct">should</em> prompt the end user
1072: for credentials. If authentication fails, and
1073: <span>request username</span> and <span>request password</span> are
1074: provided, user agents <em class="ct">must not</em> prompt the end user for
1075: credentials. [<cite><span>RFC2617</span></cite>]</p>
1.212 avankest 1076:
1.227 avankest 1077: <p class="note">End users are not prompted if credentials are provided
1.212 avankest 1078: through the <code>open()</code> API so that authors can implement their
1079: own user interface.</p>
1080:
1081: <p>If the user agent supports HTTP State Management it
1082: <em class="ct">should</em> persist, discard and send cookies (as received
1083: in the <code>Set-Cookie</code> and <code>Set-Cookie2</code> response
1084: headers, and sent in the <code>Cookie</code> header) as applicable.
1085: [<cite><span>COOKIES</span></cite>]</p>
1086:
1087: <p>If the user agent implements a HTTP cache it <em class="ct">should</em>
1.248 avankest 1088: respect <code>Cache-Control</code> request headers set by the
1089: <code>setRequestHeader()</code> (e.g., <code>Cache-Control:
1090: no-cache</code> bypasses the cache). It <em class="ct">must not</em> send
1.212 avankest 1091: <code>Cache-Control</code> or <code>Pragma</code> request headers
1.227 avankest 1092: automatically unless the end user explicitly requests such behavior
1.212 avankest 1093: (e.g. by (force-)reloading the page).</p>
1094:
1095: <p>For <code>304 Not Modified</code> responses that are a result of a
1096: user agent generated conditional request the user agent
1097: <em class="ct">must</em> act as if the server gave a <code>200 OK</code>
1098: response with the appropriate content. The user agent
1099: <em class="ct">must</em> allow <code>setRequestHeader()</code> to
1.248 avankest 1100: override automatic cache validation by setting request headers (e.g.
1101: <code>If-None-Match</code> or <code>If-Modified-Since</code>), in which
1.212 avankest 1102: case <code>304 Not Modified</code> responses <em class="ct">must</em> be
1103: passed through. [<cite><span>RFC2616</span></cite>]</p>
1104:
1105: <p>If the user agent implements server-driven content-negotiation
1106: it <em class="ct">should</em> set <code>Accept-Encoding</code> and
1.231 avankest 1107: <code>Accept-Charset</code> headers as appropriate. For
1108: <code>Accept</code> and <code>Accept-Language</code> the user agent
1109: <em class="ct">must</em> follow these constraints:</p>
1110:
1111: <ul>
1112: <li><p>Both headers <em class="ct">must not</em> be modified if they are
1113: already set through <code>setRequestHeader()</code>.</p></li>
1114:
1115: <li><p>If not set through <code>setRequestHeader()</code>
1116: <code>Accept-Language</code> <em class="ct">should</em> set as
1117: appropriate.</p></li>
1118:
1119: <li><p>If not set through <code>setRequestHeader()</code>
1120: <code>Accept</code> <em class="ct">must</em> be set with as value
1121: <code>*/*</code>.</p></li>
1122: </ul>
1123:
1124: <p>Responses <em class="ct">must</em> have the content-encodings
1125: automatically decoded. [<cite><span>RFC2616</span></cite>]</p>
1.212 avankest 1126:
1127: <p>Besides the <span>author request headers</span> user agents
1128: <em class="ct">should not</em> include additional request headers other
1.248 avankest 1129: than those mentioned above or other than those authors are not allowed to
1130: set using <code>setRequestHeader()</code>. This ensures that authors have
1131: a reasonably predictable API.</p>
1.218 avankest 1132:
1.212 avankest 1133:
1134: <h4>Infrastructure for the <code title="">send()</code> method</h4>
1.216 avankest 1135:
1136: <p>The <dfn>cookie steps</dfn> are as follows:</p>
1.218 avankest 1137:
1.216 avankest 1138: <ol>
1139: <li><p>Wait until ownership of the <span>storage mutex</span> can be
1140: taken.</p></li>
1.218 avankest 1141:
1.216 avankest 1142: <li><p>Take ownership of the <span>storage mutex</span>.</p></li>
1.218 avankest 1143:
1.216 avankest 1144: <li><p>Update the cookies. [<cite><span>COOKIES</span></cite>]</p></li>
1145:
1146: <li><p>Release the <span>storage mutex</span> so that it is once again
1147: free.</p></li>
1148: </ol>
1.218 avankest 1149:
1.216 avankest 1150: <hr>
1.218 avankest 1151:
1.219 avankest 1152: <p>The <dfn>same-origin request event rules</dfn> are as follows:</p>
1.118 avankest 1153:
1.203 avankest 1154: <dl class="switch">
1155: <dt>If the response is an HTTP redirect</dt>
1156: <dd>
1.248 avankest 1157:
1.203 avankest 1158: <p>If the redirect does not violate security (it is
1159: <span>same origin</span> for instance), infinite loop precautions, and
1160: the scheme is supported, transparently follow the redirect while
1.219 avankest 1161: observing the <span>same-origin request event rules</span>.</p>
1.248 avankest 1162:
1163: <p>Otherwise, this is a <span>network error</span>.</p>
1164:
1165:
1.203 avankest 1166:
1167: <p class="note">HTTP places requirements on the user agent regarding the
1.204 avankest 1168: preservation of the <span>request method</span> and
1.248 avankest 1169: <span>request entity body</span> during redirects, and also requires end
1170: users to be notified of certain kinds of automatic redirections.</p>
1.203 avankest 1171: <!-- XXX HTTP needs fixing here -->
1.213 avankest 1172: </dd>
1.121 avankest 1173:
1.227 avankest 1174: <dt>If the end user cancels the download</dt>
1.213 avankest 1175: <dd><p>This is an <span>abort error</span>.</p></dd>
1.60 avankest 1176:
1.214 avankest 1177: <dt>In case of network errors</dt>
1.213 avankest 1178: <dd>
1179: <p>In case of DNS errors, TLS negotiation failure, or other type of
1180: network errors, this is a <span>network error</span>. Do not request any
1.227 avankest 1181: kind of end user interaction.</p>
1.121 avankest 1182:
1.213 avankest 1183: <p class="note">This does not include HTTP responses that indicate
1184: some type of error, such as HTTP status code 410.</p>
1185: </dd>
1.60 avankest 1186:
1.248 avankest 1187:
1188:
1.213 avankest 1189: <dt>Once all HTTP headers have been received and the
1190: <span>asynchronous flag</span> is true</dt>
1191: <dd><p><span>Switch to the HEADERS_RECEIVED state</span>.</p></dd>
1.186 avankest 1192:
1.220 avankest 1193: <dt>Once the first byte (or more) of the
1194: <span>response entity body</span> has been received and the
1195: <span>asynchronous flag</span> is true</dt>
1196: <dt>If there is no <span>response entity body</span> and the
1.213 avankest 1197: <span>asynchronous flag</span> is true</dt>
1.215 avankest 1198: <dd><p><span>Switch to the LOADING state</span>.</p></dd>
1.220 avankest 1199:
1200: <dt>Once the whole <span>response entity body</span> has been
1201: received</dt>
1.224 avankest 1202: <dt>If there is no <span>response entity body</span> and the
1203: <span>asynchronous flag</span> is false or the state is
1.221 avankest 1204: <span title="LOADING state">LOADING</span></dt>
1.220 avankest 1205: <dd><p><span>Switch to the DONE state</span>.</p></dd>
1.213 avankest 1206: </dl>
1.218 avankest 1207:
1.248 avankest 1208:
1209:
1.213 avankest 1210: <hr>
1.218 avankest 1211:
1.241 avankest 1212: <p>When something is said to be a <dfn>network error</dfn> run the
1213: <span>request error</span> steps for exception
1214: <code>NETWORK_ERR</code>.</p>
1215:
1216: <p>When something is said to be an <dfn>abort error</dfn> run the
1217: <span>request error</span> steps for exception
1218: <code>ABORT_ERR</code>.</p>
1.60 avankest 1219:
1.248 avankest 1220:
1221:
1.242 avankest 1222: <p>When something is said to be a <dfn>request error</dfn> for
1.248 avankest 1223: exception <var>exception</var> run these
1224: steps:</p>
1.12 avankest 1225:
1.213 avankest 1226: <ol>
1.250 avankest 1227: <!-- XXX should cancel network activity here as well for abort/timeout cases (and maybe others); clean up task queue? -->
1228:
1.213 avankest 1229: <li><p>Set the <span>response entity body</span> to null.</p></li>
1.203 avankest 1230:
1.213 avankest 1231: <li><p>Set the the <span>error flag</span> to true.</p></li>
1.12 avankest 1232:
1.213 avankest 1233: <li><p>Empty the list of <span>author request headers</span>.</p></li>
1.203 avankest 1234:
1.213 avankest 1235: <li><p>Switch the state to <span title="DONE state">DONE</span>.</p></li>
1.203 avankest 1236:
1.241 avankest 1237: <li><p>If the <span>asynchronous flag</span> is false raise an
1238: <var>exception</var> exception and terminate the overall set of
1.213 avankest 1239: steps.</p></li>
1.203 avankest 1240:
1.248 avankest 1241: <li>
1.249 avankest 1242: <p><span>Dispatch a <code>readystatechange</code> event</span>.</p>
1.248 avankest 1243:
1244: <p class="note">At this point it is clear that the
1245: <span>asynchronous flag</span> is true.</p>
1246: </li>
1247:
1248:
1.203 avankest 1249:
1.248 avankest 1250: <li><p>Terminate the overall algorithm.</p></li>
1.213 avankest 1251: </ol>
1.203 avankest 1252:
1.248 avankest 1253:
1254: <p class="note">A future version of this specification will dispatch an
1255: <code>error</code>/<code>abort</code> event here as well. (Depending on
1256: the type of error.)</p>
1257:
1.203 avankest 1258:
1.213 avankest 1259: <hr>
1.203 avankest 1260:
1.213 avankest 1261: <p>When it is said to
1262: <dfn id="switch-headers-received">switch to the HEADERS_RECEIVED state</dfn>
1263: run these steps:</p>
1.203 avankest 1264:
1.213 avankest 1265: <ol>
1266: <li><p>Switch the state to <span title="HEADERS_RECEIVED state">HEADERS_RECEIVED</span>.</p></li>
1.203 avankest 1267:
1.249 avankest 1268: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.213 avankest 1269: </ol>
1.218 avankest 1270:
1.213 avankest 1271: <hr>
1.60 avankest 1272:
1.213 avankest 1273: <p>When it is said to
1274: <dfn id="switch-loading">switch to the LOADING state</dfn> run these
1275: steps:</p>
1.218 avankest 1276:
1.213 avankest 1277: <ol>
1278: <li><p>Switch the state to <span title="LOADING state">LOADING</span>.</p></li>
1.203 avankest 1279:
1.249 avankest 1280: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.213 avankest 1281: </ol>
1.218 avankest 1282:
1.216 avankest 1283: <hr>
1284:
1285: <p>When it is said to
1286: <dfn id="switch-done">switch to the DONE state</dfn> run these steps:</p>
1.218 avankest 1287:
1.216 avankest 1288: <ol>
1289: <li><p>Switch the state to <span title="DONE state">DONE</span>.</p></li>
1290:
1.248 avankest 1291: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1292:
1.220 avankest 1293:
1.216 avankest 1294: </ol>
1.218 avankest 1295:
1.248 avankest 1296:
1297:
1.203 avankest 1298:
1299: <h4>The <code title="">abort()</code> method</h4>
1300:
1301: <p>When the <dfn id="abort"><code>abort()</code></dfn> method is invoked,
1.217 avankest 1302: the user agent <em class="ct">must</em> run these steps (unless otherwise
1303: noted):</p>
1.12 avankest 1304:
1.203 avankest 1305: <ol>
1306: <li><p><span title="abort send()">Abort the <code>send()</code> algorithm</span>.</p></li>
1307:
1308: <li><p>The user agent <em class="ct">should</em> cancel any network
1309: activity for which the object is responsible.</p></li>
1.252 ! avankest 1310:
! 1311: <li><p>If there are any <span title="task">tasks</span> from the object's
! 1312: <span><code>XMLHttpRequest</code> task source</span> in one of the
! 1313: <span>task queues</span>, then remove those tasks.</p></li>
1.203 avankest 1314:
1315: <li><p>Set the <span>response entity body</span> to null.</p></li>
1316:
1.252 ! avankest 1317: <li><p>Empty the list of <span>author request headers</span>.</p></li>
! 1318:
1.203 avankest 1319: <li><p>Set the <span>error flag</span> to true.</p></li>
1320:
1321: <li>
1322: <p>If the state is <span title="UNSENT state">UNSENT</span>,
1323: <span title="OPENED state">OPENED</span> with the
1324: <span><code>send()</code> flag</span> being false, or
1325: <span title="DONE state">DONE</span> go to the next step.</p>
1.12 avankest 1326:
1.203 avankest 1327: <p>Otherwise run these substeps:</p>
1.58 avankest 1328:
1329: <ol>
1.203 avankest 1330: <li><p>Switch the state to <span title="DONE state">DONE</span>.</p></li>
1.170 avankest 1331:
1.203 avankest 1332: <li><p>Set the <span><code>send()</code> flag</span> to false.</p></li>
1.96 avankest 1333:
1.203 avankest 1334: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.248 avankest 1335:
1336:
1.58 avankest 1337: </ol>
1.250 avankest 1338:
1.248 avankest 1339:
1.250 avankest 1340: <p class="note">A future version of this specification will dispatch an
1341: <code title="abort-event">abort</code> event here.</p>
1.248 avankest 1342:
1.203 avankest 1343: </li>
1344:
1345: <li>
1346: <p>Switch the state to <span title="UNSENT state">UNSENT</span>.</p>
1347:
1348: <p class="note">No <code>readystatechange</code> event is dispatched.</p>
1349: </li>
1350: </ol>
1351:
1352:
1353:
1.205 avankest 1354: <h3 id="response">Response</h3>
1.203 avankest 1355:
1356:
1357: <h4>The <code title="">status</code> attribute</h4>
1358:
1359: <p>The <dfn id="status"><code>status</code></dfn> attribute
1.222 avankest 1360: <em class="ct">must</em> return the result of running these steps:</p>
1.226 avankest 1361:
1.222 avankest 1362: <ol>
1363: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1364: <span title="OPENED state">OPENED</span> return 0 and terminate these
1.222 avankest 1365: steps.</p></li>
1366:
1.239 avankest 1367: <li><p>If the <span>error flag</span> is true return 0 and terminate
1368: these steps.</p></li>
1.222 avankest 1369:
1370: <li><p>Return the HTTP status code.</p></li>
1.248 avankest 1371: </ol>
1.203 avankest 1372:
1373:
1374: <h4>The <code title="">statusText</code> attribute</h4>
1375:
1376: <p>The <dfn id="statustext"><code>statusText</code></dfn> attribute
1.222 avankest 1377: <em class="ct">must</em> return the result of running these steps:</p>
1378:
1379: <ol>
1380: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1381: <span title="OPENED state">OPENED</span> return the empty string and
1382: terminate these steps.</p></li>
1.222 avankest 1383:
1384: <li><p>If the <span>error flag</span> is true return the empty string and
1385: terminate these steps.</p></li>
1386:
1387: <li><p>Return the HTTP status text.</p></li>
1388: </ol>
1.203 avankest 1389:
1390:
1391: <h4>The <code title="">getResponseHeader()</code> method</h4>
1392:
1393: <p>When the
1394: <dfn id="getresponseheader" title="getresponseheader"><code>getResponseHeader(<var>header</var>)</code></dfn>
1.217 avankest 1395: is invoked, the user agent <em class="ct">must</em> run these steps:</p>
1.203 avankest 1396:
1397: <ol>
1398: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1399: <span title="OPENED state">OPENED</span> return null and terminate these
1.203 avankest 1400: steps.</p></li>
1401:
1.239 avankest 1402: <li><p>If the <span>error flag</span> is true return null
1.203 avankest 1403: and terminate these steps.</p></li>
1404:
1405: <li><p>If <var>header</var> is an <span>ASCII case-insensitive</span>
1406: match for <code>Set-Cookie</code> or <code>Set-Cookie2</code> return
1.239 avankest 1407: null and terminate these steps.</p></li>
1.203 avankest 1408:
1409: <li><p>If <var>header</var> is an <span>ASCII case-insensitive</span>
1410: match for multiple HTTP response headers, return the values of these
1411: headers as a single concatenated string separated from each other by a
1412: U+002C COMMA U+0020 SPACE character pair and terminate these
1413: steps.</p></li>
1414:
1415: <li><p>If <var>header</var> is an <span>ASCII case-insensitive</span>
1416: match for a single HTTP response header, return the value of that header
1417: and terminate these steps.</p></li>
1418:
1.239 avankest 1419: <li><p>Return null.</p></li>
1.203 avankest 1420: </ol>
1421:
1.248 avankest 1422:
1423:
1.203 avankest 1424: <div class="example">
1.250 avankest 1425:
1426: <p>For the following script:</p>
1427:
1428: <pre><code>var client = new XMLHttpRequest();
1429: client.open("GET", "unicorns-are-teh-awesome.txt", true);
1.5 avankest 1430: client.send();
1.12 avankest 1431: client.onreadystatechange = function() {
1.250 avankest 1432: if(this.readyState == 2) {
1433: print(client.getResponseHeader("Content-Type"));
1434: }
1435: }</code></pre>
1436:
1437: <p>The <code>print()</code> function will get to process something
1438: like:</p>
1.5 avankest 1439:
1.250 avankest 1440: <pre><code>text/plain; charset=UTF-8</code></pre>
1.203 avankest 1441: </div>
1.12 avankest 1442:
1443:
1.203 avankest 1444: <h4>The <code title="">getAllResponseHeaders()</code> method</h4>
1.14 avankest 1445:
1.203 avankest 1446: <p>When the
1447: <dfn id="getallresponseheaders"><code>getAllResponseHeaders()</code></dfn>
1448: method is invoked, the user agent <em class="ct">must</em> run the
1449: following steps:</p>
1.58 avankest 1450:
1.203 avankest 1451: <ol>
1452: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1453: <span title="OPENED state">OPENED</span> return the empty string and
1454: terminate these steps.</p></li>
1.203 avankest 1455:
1456: <li><p>If the <span>error flag</span> is true return the empty string and
1457: terminate these steps.</p></li>
1458:
1459: <li><p>Return all the HTTP headers, excluding headers that are an
1460: <span>ASCII case-insensitive</span> match for <code>Set-Cookie</code> or
1461: <code>Set-Cookie2</code>, as a single string, with each header line
1462: separated by a U+000D CR U+000A LF pair excluding the status line, and
1463: with each header name and header value separated by a
1464: U+003A COLON U+0020 SPACE pair.</p></li>
1465: </ol>
1.58 avankest 1466:
1.250 avankest 1467:
1468:
1.203 avankest 1469: <div class="example">
1.250 avankest 1470: <p>For the following script:</p>
1471:
1472: <pre><code>var client = new XMLHttpRequest();
1473: client.open("GET", "narwhals-too.txt", true);
1.5 avankest 1474: client.send();
1.12 avankest 1475: client.onreadystatechange = function() {
1.179 avankest 1476: if(this.readyState == 2) {
1.203 avankest 1477: print(this.getAllResponseHeaders());
1.12 avankest 1478: }
1.250 avankest 1479: }</code></pre>
1480:
1481: <p>The <code>print()</code> function will get to process something
1482: like:</p>
1.1 avankest 1483:
1.250 avankest 1484: <pre><code>Date: 2004年10月24日 04:58:38 GMT
1.203 avankest 1485: Server: Apache/1.3.31 (Unix)
1486: Keep-Alive: timeout=15, max=99
1487: Connection: Keep-Alive
1488: Transfer-Encoding: chunked
1489: Content-Type: text/plain; charset=utf-8</code></pre>
1490: </div>
1491:
1.250 avankest 1492:
1.203 avankest 1493:
1494: <h4>Response Entity Body</h4>
1495:
1.248 avankest 1496: <p>The <dfn id="response-mime-type">response MIME type</dfn> is the MIME
1497: type the <code>Content-Type</code> header contains without any
1498: parameters or null if the header could not be parsed properly or was
1499: omitted. The <dfn id="override-mime-type">override MIME type</dfn> is
1500: always null. <dfn id="final-mime-type">Final MIME type</dfn> is the
1501: override MIME type unless that is null in which case it is the response
1502: MIME type.</p>
1503:
1504: <p>The <dfn id="response-charset">response charset</dfn> is the value of
1505: the <code>charset</code> parameter of the <code>Content-Type</code> header
1506: or null if there was no <code>charset</code> parameter or if
1507: the header could not be parsed properly or was omitted. The
1508: <dfn id="override-charset">override charset</dfn> is always null.
1509: <dfn id="final-charset">Final charset</dfn> is the override charset unless
1510: that is null in which case it is the response charset.</p>
1.250 avankest 1511:
1.248 avankest 1512:
1513: <p class="note"><span>Override MIME type</span> and
1514: <span>override charset</span> are introduced here solely to make editing
1515: several levels of XMLHttpRequest simultaneously somewhat easier. Apologies
1516: for any confusion they might cause.</p>
1517:
1.250 avankest 1518:
1.248 avankest 1519: <hr>
1520:
1.203 avankest 1521: <p>The <dfn id="response-entity-body">response entity body</dfn> is the
1.248 avankest 1522: fragment of the <span>entity body</span> received so far (LOADING state) or
1523: the complete entity body (DONE state). If there is no entity body the
1524: response entity body is null.</p>
1.250 avankest 1525:
1.203 avankest 1526: <hr>
1527:
1528: <p>The <dfn id="text-response-entity-body">text response entity body</dfn>
1.248 avankest 1529: is a <code>DOMString</code> representing the <span>response entity
1530: body</span>. The text response entity body is the return value of the
1.203 avankest 1531: following algorithm:</p>
1532:
1533: <ol>
1.248 avankest 1534: <li><p>If the response entity body is null return the empty string and
1535: terminate these steps.</p>
1536:
1537: <li><p>Let <var>charset</var> be the <span>final charset</span>.</p></li>
1.203 avankest 1538:
1.248 avankest 1539: <li><p>Let <var>mime</var> be the <span>final MIME type</span>.</p></li>
1.203 avankest 1540:
1.248 avankest 1541: <li><p>If <var>charset</var> is null and <var>mime</var> is null,
1.203 avankest 1542: <code>text/xml</code>, <code>application/xml</code> or ends in
1.248 avankest 1543: <code title="">+xml</code> use the rules set forth in the XML
1544: specifications to determine the character encoding. Let
1545: <var>charset</var> be the determined character encoding.</p></li>
1546:
1547: <li><p>If <var>charset</var> is null and <var>mime</var> is
1548: <code>text/html</code> follow the rules set forth in the HTML
1549: specification to determine the character encoding. Let
1.203 avankest 1550: <var>charset</var> be the determined character encoding.
1551: [<cite><span>HTML5</span></cite>]</p></li>
1552:
1553: <li>
1554: <p>If <var>charset</var> is null then, for each of the rows in the
1555: following table, starting with the first one and going down, if the first
1556: bytes of <var>bytes</var> match the bytes given in the first column, then
1557: let <var>charset</var> be the encoding given in the cell in the second
1558: column of that row. If there is no match <var>charset</var> remains
1559: null.</p>
1560:
1561: <table>
1562: <thead>
1563: <tr>
1564: <th>Bytes in Hexadecimal
1565: <th>Description
1.237 avankest 1566: <tbody>
1.203 avankest 1567: <tr>
1568: <td>FE FF
1569: <td>UTF-16BE BOM
1570: <tr>
1571: <td>FF FE
1572: <td>UTF-16LE BOM
1573: <tr>
1574: <td>EF BB BF
1.237 avankest 1575: <td>UTF-8 BOM
1.203 avankest 1576: </table>
1577: </li>
1578:
1579: <li><p>If <var>charset</var> is null let <var>charset</var> be
1580: UTF-8.</p></li>
1581:
1582: <li><p>Return the result of decoding the response entity body using
1583: <var>charset</var>. Replace bytes or sequences of bytes that are not
1.248 avankest 1584: valid accordng to the <var>charset</var> with a single
1585: U+FFFD REPLACEMENT CHARACTER character.</p></li>
1.203 avankest 1586: </ol>
1587:
1588: <p class="note">Authors are strongly encouraged to encode their resources
1589: using UTF-8.</p>
1.248 avankest 1590:
1.203 avankest 1591: <hr>
1592:
1.248 avankest 1593: <p>The <dfn id="document-response-entity-body">document response entity
1594: body</dfn> is either a <code>Document</code> representing the
1595: <span>response entity body</span> or null. The document
1596: response entity body is the return value of the following algorithm:</p>
1.12 avankest 1597:
1.203 avankest 1598: <ol>
1599: <li><p>If the <span>response entity body</span> is null terminate these
1.239 avankest 1600: steps and return null.</p></li>
1.12 avankest 1601:
1.248 avankest 1602: <li><p>If <span>final MIME type</span> is not null,
1603: <code>text/xml</code>,
1604: <code>application/xml</code>, and does not end in
1605: <code title="">+xml</code> terminate these steps and return
1606: null.</li>
1607:
1608:
1.203 avankest 1609:
1610: <li>
1.248 avankest 1611: <p>Let <var>document</var> be an object implementing the
1612: <code>Document</code> interface that represents the result of parsing
1613: the response entity body into a document tree following the rules from
1614: the XML specifications. If this fails (unsupported character encoding,
1615: namespace well-formedness error et cetera) terminate these steps return
1616: null. [<cite><span>XML</span></cite>]</p>
1617:
1618: <p class="note">Scripts in the resulting document tree will not be executed,
1619: resources referenced will not be loaded and no associated XSLT will be
1620: applied.</p>
1.203 avankest 1621: </li>
1.88 avankest 1622:
1.248 avankest 1623:
1624:
1625: <li><p>Return <var>document</var>.</p></li>
1.203 avankest 1626: </ol>
1.12 avankest 1627:
1628:
1.248 avankest 1629:
1630:
1631:
1.203 avankest 1632: <h4>The <code title="">responseText</code> attribute</h4>
1.12 avankest 1633:
1.203 avankest 1634: <p>The <dfn id="responsetext"><code>responseText</code></dfn> attribute
1.217 avankest 1635: <em class="ct">must</em> return the result of running these steps:</p>
1.79 avankest 1636:
1.203 avankest 1637: <ol>
1.248 avankest 1638: <li><p>If the state is not <span title="LOADING state">LOADING</span> or
1639: <span title="DONE state">DONE</span> return the empty string and
1.203 avankest 1640: terminate these steps.</p></li>
1.75 avankest 1641:
1.203 avankest 1642: <li><p>Return the <span>text response entity body</span>.</p></li>
1643: </ol>
1.12 avankest 1644:
1645:
1.203 avankest 1646: <h4>The <code title="">responseXML</code> attribute</h4>
1.12 avankest 1647:
1.203 avankest 1648: <p>The <dfn id="responsexml"><code>responseXML</code></dfn> attribute
1.217 avankest 1649: <em class="ct">must</em> return the result of running these steps:</p>
1.12 avankest 1650:
1.203 avankest 1651: <ol>
1652: <li><p>If the state is not <span title="DONE state">DONE</span> return
1.239 avankest 1653: null and terminate these steps.</p></li>
1.12 avankest 1654:
1.248 avankest 1655: <li><p>Return the <span>document response entity body</span>.</p></li>
1.203 avankest 1656: </ol>
1.121 avankest 1657:
1.248 avankest 1658:
1659:
1.12 avankest 1660:
1.240 avankest 1661: <h2 id="exceptions">Exceptions</h2>
1.24 avankest 1662:
1.138 avankest 1663: <p>Several algorithms in this specification may result in an exception
1664: being thrown. These exceptions are all part of the group
1.185 avankest 1665: <code>ExceptionCode</code> and use the <code>DOMException</code> object,
1.138 avankest 1666: which is defined in DOM Level 3 Core. In addition this specification
1667: extends the <code>ExceptionCode</code> group with several new
1668: constants as indicated below. [<cite><span>DOM3Core</span></cite>]</p>
1.203 avankest 1669:
1.193 avankest 1670: <p class="note">Thus, exceptions used by this specification and not
1671: defined in this section are defined by DOM Level 3 Core.</p>
1.31 avankest 1672:
1.138 avankest 1673: <pre class="idl">const unsigned short <span>SECURITY_ERR</span> = 18;
1.199 avankest 1674: const unsigned short <span>NETWORK_ERR</span> = 19;
1675: const unsigned short <span>ABORT_ERR</span> = 20;</pre>
1.31 avankest 1676:
1.138 avankest 1677: <p>The <dfn id="security-err"><code>SECURITY_ERR</code></dfn> exception is
1678: raised if an attempt is made to perform an operation or access some data
1679: in a way that would be a security risk or a violation of the user agent's
1680: security policy.</p>
1681:
1682: <!-- http://lists.w3.org/Archives/Public/public-webapi/2006May/0027.html -->
1683:
1.33 avankest 1684: <p>The <dfn id="network-err"><code>NETWORK_ERR</code></dfn> exception is
1.138 avankest 1685: raised when a network error occurs in synchronous requests.</p>
1.121 avankest 1686:
1.138 avankest 1687: <p>The <dfn id="abort-err"><code>ABORT_ERR</code></dfn> exception is
1688: raised when the user aborts a request in synchronous requests.</p>
1.248 avankest 1689:
1690:
1.203 avankest 1691:
1.240 avankest 1692: <p class="note">These exceptions will be folded into an update of
1.199 avankest 1693: DOM Level 3 Core in due course, as they are appropriate for other API
1694: specifications as well.</p>
1.121 avankest 1695:
1.248 avankest 1696:
1.29 avankest 1697: <h2 class="no-num" id="notcovered">Not in this Specification</h2>
1698:
1.143 avankest 1699: <p><em>This section is non-normative.</em></p>
1.29 avankest 1700:
1.72 avankest 1701: <p>This specification does not include the following features which are
1702: being considered for a future version of this specification:</p>
1.29 avankest 1703:
1704: <ul>
1705: <li><code>load</code> event and <code>onload</code> attribute;</li>
1706: <li><code>error</code> event and <code>onerror</code> attribute;</li>
1707: <li><code>progress</code> event and <code>onprogress</code> attribute;</li>
1708: <li><code title="">abort</code> event and <code>onabort</code> attribute;</li>
1709: <li>Timers have been suggested, perhaps an <code>ontimeout</code>
1710: attribute;</li>
1711: <li>Property to disable following redirects;</li>
1.30 avankest 1712: <li><code title="">responseXML</code> for <code>text/html</code>
1713: documents;</li>
1.203 avankest 1714: <li>Cross-origin <code title="">XMLHttpRequest</code>;</li>
1.87 avankest 1715: <li><code>responseBody</code> to deal with byte streams;</li>
1.114 avankest 1716: <li><code>overrideMimeType</code> to fix up MIME types;</li>
1.87 avankest 1717: <li><code>getRequestHeader()</code> and
1718: <code>removeRequestHeader()</code>.</li>
1.29 avankest 1719: </ul>
1.248 avankest 1720:
1.29 avankest 1721:
1.203 avankest 1722:
1.248 avankest 1723:
1724:
1.203 avankest 1725:
1.248 avankest 1726: <h2 class="no-num" id="references">References</h2>
1.203 avankest 1727:
1.177 avankest 1728: <p>Unless marked "Non-normative" these references are normative.</p>
1.11 avankest 1729:
1.6 avankest 1730: <dl>
1.230 avankest 1731: <dt>[<dfn id="ref-cookies">COOKIES</dfn>]</dt>
1.203 avankest 1732: <dd><cite><a href="http://ietf.org/rfc/rfc2109">HTTP State Management
1733: Mechanism</a></cite>, D. Kristol, L. Montulli, editors. IETF, February
1734: 1997.</dd>
1735: <dd><cite><a href="http://ietf.org/rfc/rfc2965">HTTP State Management
1736: Mechanism</a></cite>, D. Kristol, L. Montulli, editors. IETF, October
1.218 avankest 1737: 2000.</dd>
1.211 avankest 1738:
1.203 avankest 1739: <!-- XXX These specs do not match reality. Also, the latter obsoletes the
1740: former -->
1741:
1.248 avankest 1742:
1743:
1.155 avankest 1744: <dt>[<dfn id="ref-dom2events">DOM2Events</dfn>]</dt>
1745: <dd><cite><a href="http://www.w3.org/TR/DOM-Level-2-Events/">Document
1.160 avankest 1746: Object Model (DOM) Level 2 Events Specification</a></cite>, T. Pixley,
1747: editor. W3C, November 2000.</dd>
1.155 avankest 1748:
1.145 avankest 1749: <dt>[<dfn id="ref-dom3core">DOM3Core</dfn>]</dt>
1.11 avankest 1750: <dd><cite><a href="http://www.w3.org/TR/DOM-Level-3-Core">Document Object
1.92 avankest 1751: Model (DOM) Level 3 Core Specification</a></cite>, A. Le Hors, P. Le
1.139 avankest 1752: Hégaret, L. Wood, G. Nicol, J. Robie, M. Champion, S. Byrne,
1753: editors. W3C, April 2004.</dd>
1.11 avankest 1754:
1.117 avankest 1755: <dt>[<dfn id="ref-ecmascript">ECMAScript</dfn>]</dt>
1.92 avankest 1756: <dd><cite><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">ECMAScript
1.248 avankest 1757: Language Specification</a></cite>, Third Edition. ECMA, December
1758: 1999.</dd>
1759:
1760:
1.171 avankest 1761:
1.145 avankest 1762: <dt>[<dfn id="ref-html5">HTML5</dfn>]</dt>
1.250 avankest 1763: <dd><cite><a href="http://www.w3.org/html/wg/html5/">HTML5</a></cite>
1764: (work in progress), I. Hickson, D. Hyatt, editors. W3C, 2010.</dd>
1765: <dd><cite><a href="http://www.whatwg.org/specs/html5/current-work/">HTML5</a></cite>
1766: (work in progress), I. Hickson, editor. WHATWG, 2010.</dd>
1.198 avankest 1767:
1768: <dt>[<dfn id="ref-httpverbsec">HTTPVERBSEC</dfn>]</dt>
1.248 avankest 1769: <dd>(Non-normative)
1770: <cite><a href="http://www.kb.cert.org/vuls/id/867593">Multiple vendors'
1771: web servers enable HTTP TRACE method by default</a></cite>, US-CERT.</dd>
1772: <dd>(Non-normative)
1773: <cite><a href="http://www.kb.cert.org/vuls/id/288308">Microsoft Internet
1774: Information Server (IIS) vulnerable to cross-site scripting via HTTP
1775: TRACK method</a></cite>, US-CERT.</dd>
1776: <dd>(Non-normative)
1777: <cite><a href="http://www.kb.cert.org/vuls/id/150227">HTTP proxy default
1778: configurations allow arbitrary TCP connections</a></cite>, US-CERT.</dd>
1779:
1780:
1781:
1782: <dt>[<dfn id="ref-rfc2046">RFC2046</dfn>]</dt>
1783: <dd><cite><a href="http://ietf.org/rfc/rfc2046">Multipurpose Internet Mail
1784: Extensions (MIME) Part Two: Media Types</a></cite>, N. Freed, N.
1785: Borenstein, editors. IETF, November 1996.</dd>
1.198 avankest 1786:
1.145 avankest 1787: <dt>[<dfn id="ref-rfc2119">RFC2119</dfn>]</dt>
1.117 avankest 1788: <dd><cite><a href="http://ietf.org/rfc/rfc2119">Key words for use in RFCs to
1789: Indicate Requirement Levels</a></cite>, S. Bradner. IETF, March 1997.</dd>
1.12 avankest 1790:
1.248 avankest 1791: <dt>[<dfn id="rfc-rfc2616">RFC2616</dfn>]</dt>
1.11 avankest 1792: <dd><cite><a href="http://ietf.org/rfc/rfc2616">Hypertext Transfer Protocol
1.92 avankest 1793: -- HTTP/1.1</a></cite>, R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L.
1794: Masinter, P. Leach, T. Berners-Lee, editors. IETF, June 1999.</dd>
1.12 avankest 1795:
1.37 avankest 1796: <dt>[<dfn id="ref-rfc2617">RFC2617</dfn>]</dt>
1.11 avankest 1797: <dd><cite><a href="http://ietf.org/rfc/rfc2617">HTTP Authentication: Basic
1.92 avankest 1798: and Digest Access Authentication</a></cite>, P. Hallam-Baker, J.
1799: Hostetler, S. Lawrence, P. Leach, A. Luotonen, L. Stewart, editors. IETF,
1800: June 1999.</dd>
1.12 avankest 1801:
1.37 avankest 1802: <dt>[<dfn id="ref-rfc3986">RFC3986</dfn>]</dt>
1.11 avankest 1803: <dd><cite><a href="http://ietf.org/rfc/rfc3986">Uniform Resource Identifier
1.92 avankest 1804: (URI): Generic Syntax</a></cite>, T. Berners-Lee, R. Fielding, L. Masinter,
1805: editors. IETF, January 2005.</dd>
1.184 avankest 1806:
1.248 avankest 1807: <dt>[<dfn id=ref-rfc3987>RFC3987</dfn>]</dt>
1808: <dd><cite><a href="http://ietf.org/rfc/rfc3987">Internationalized
1809: Resource Identifiers (IRIs)</a></cite>, M. Duerst, M. Suignard, editors.
1810: IETF, January 2005. L. Masinter, editors. IETF, January 2005.</dd>
1811:
1.203 avankest 1812: <dt>[<dfn id="ref-webidl">WebIDL</dfn>]</dt>
1.200 avankest 1813: <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web
1.250 avankest 1814: IDL</a></cite> (work in progress), C. McCormack, editor. W3C, 2010.</dd> <!-- XXX add Sam -->
1.181 avankest 1815:
1.92 avankest 1816: <dt>[<dfn id="ref-xml">XML</dfn>]</dt>
1817: <dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup Language
1.203 avankest 1818: (XML) 1.0 (Fifth Edition)</a></cite>, T. Bray, J. Paoli, C.
1819: Sperberg-McQueen, E. Maler, F. Yergeau, editors. W3C, November 2008.</dd>
1.92 avankest 1820: <dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in XML
1.117 avankest 1821: (Second Edition)</a></cite>, T. Bray, D. Hollander, A. Layman, R. Tobin,
1.250 avankest 1822: editors. W3C, August 2006.</dd> <!--XXX this was updated-->
1.1 avankest 1823: </dl>
1.11 avankest 1824:
1.203 avankest 1825:
1826:
1.130 avankest 1827: <h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
1.11 avankest 1828:
1.159 avankest 1829: <p>The editor would like to thank
1.12 avankest 1830:
1.163 avankest 1831: Addison Phillips,
1.159 avankest 1832: Ahmed Kamel,
1833: Alex Hopmann,
1834: Alex Vincent,
1835: Alexey Proskuryakov,
1836: Asbjørn Ulsberg,
1837: Boris Zbarsky,
1838: Björn Höhrmann,
1839: Cameron McCormack,
1840: Christophe Jolif,
1841: Charles McCathieNevile,
1842: Dan Winship,
1.248 avankest 1843: David Andersson,
1.159 avankest 1844: David Håsäther,
1.248 avankest 1845: David Levin,
1.159 avankest 1846: Dean Jackson,
1847: Denis Sureau,
1848: Doug Schepers,
1849: Douglas Livingstone,
1850: Elliotte Harold,
1851: Eric Lawrence,
1.196 avankest 1852: Erik Dahlström,
1.163 avankest 1853: Geoffrey Sneddon,
1.159 avankest 1854: Gideon Cohn,
1855: Gorm Haug Eriksen,
1.247 avankest 1856: Håkon Wium Lie,
1.159 avankest 1857: Hallvord R. M. Steen,
1.247 avankest 1858: Huub Schaeks,
1.159 avankest 1859: Ian Davis,
1860: Ian Hickson,
1861: Ivan Herman,
1862: Jeff Walden,
1863: Jens Lindström,
1864: Jim Deegan,
1865: Jim Ley,
1866: Joe Farro,
1867: Jonas Sicking,
1868: Julian Reschke,
1869: Karl Dubost,
1.175 avankest 1870: Lachlan Hunt,
1.159 avankest 1871: Maciej Stachowiak,
1872: Magnus Kristiansen,
1873: Marc Hadley,
1874: Marcos Caceres,
1875: Mark Baker,
1.203 avankest 1876: Mark Birbeck,
1.159 avankest 1877: Mark Nottingham,
1.248 avankest 1878: Martin Hassman,
1.159 avankest 1879: Mohamed Zergaoui,
1.248 avankest 1880: Olly Pettay,
1.159 avankest 1881: Pawel Glowacki,
1.231 avankest 1882: Peter Michaux,
1.159 avankest 1883: Robin Berjon,
1.248 avankest 1884: Rune Halvorsen,
1.159 avankest 1885: Ruud Steltenpool,
1886: Simon Pieters,
1887: Stewart Brodie,
1888: Sunava Dutta,
1.186 avankest 1889: Thomas Roessler,
1.203 avankest 1890: Tom Magliery, and
1.159 avankest 1891: Zhenbin Xu
1.181 avankest 1892:
1.159 avankest 1893: for their contributions to this specification.</p>
1.12 avankest 1894:
1.1 avankest 1895: <p>Special thanks to the Microsoft employees who first implemented the
1.143 avankest 1896: <code title="">XMLHttpRequest</code> interface, which was first widely
1897: deployed by the Windows Internet Explorer browser.</p>
1.12 avankest 1898:
1.143 avankest 1899: <p>Special thanks also to the WHATWG for drafting an initial version of
1900: this specification in their Web Applications 1.0 document (now renamed to
1.250 avankest 1901: HTML5). [<cite><span>HTML5</span></cite>]</p>
1.12 avankest 1902:
1.143 avankest 1903: <p>Thanks also to all those who have helped to improve this specification
1904: by sending suggestions and corrections. (Please, keep bugging us with your
1.22 avankest 1905: issues!)</p>
1.1 avankest 1906: </body>
1907: </html>
1.211 avankest 1908:
Webmaster