Annotation of 2006/webapi/XMLHttpRequest/Overview.src.html, revision 1.267
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.259 avankest 214: <em class="ct">should</em>, <em class="ct">should not</em>, and
215: <em class="ct">may</em> in this document are to be interpreted as
216: described in RFC 2119. [<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:
1.233 avankest 303: <p><dfn id="dfn-obtain-unicode">convert a DOMString to a sequence of Unicode characters</dfn>
304: is defined by the Web IDL specification.
305: [<cite><span>WebIDL</span></cite>]</p>
1.266 avankest 306:
307: <p>The term <dfn>user credentials</dfn> for the purposes of this
308: specification means cookies, HTTP authentication, and client-side SSL
309: certificates. Specifically it does not refer to proxy authentication or
310: the <code title="http-origin">Origin</code> header.
311: <a href="#ref-cookies">[COOKIES]</a> <!-- XXX ref? --></p>
1.248 avankest 312:
1.200 avankest 313: <p>The terms and algorithms
1.257 avankest 314: <dfn id="url-fragment"><code><fragment></code></dfn>,
315: <dfn id="url-scheme"><code><scheme></code></dfn>,
1.265 avankest 316: <dfn id="cookie-free-document-object">cookie-free <code>Document</code> object</dfn>,
1.203 avankest 317: <dfn id="document-base-url">document base URL</dfn>,
1.244 avankest 318: <dfn id="document-character-encoding">document's character encoding</dfn>,
1.205 avankest 319: <dfn id="event-handler-attributes-0">event handler attributes</dfn>,
1.203 avankest 320: <dfn id="event-handler-event-type">event handler event type</dfn>,
1.260 avankest 321: <dfn id="fetch">fetch</dfn>,
1.203 avankest 322: <dfn id="fully-active">fully active</dfn>,
1.206 avankest 323: <dfn id="function"><code>Function</code></dfn>,
1.225 avankest 324: <dfn id="dom-innerhtml" title="dom-innerHTML"><code>innerHTML</code></dfn>,
1.200 avankest 325: <dfn id="origin">origin</dfn>,
1.232 avankest 326: <dfn id="preferred-mime-name">preferred MIME name</dfn>,
1.203 avankest 327: <dfn id="resolve-a-url">resolve a URL</dfn>,
328: <dfn id="same-origin">same origin</dfn>,
329: <dfn id="storage-mutex">storage mutex</dfn>,
330: <dfn id="task">task</dfn>,
331: <dfn id="task-source">task source</dfn>,
1.252 avankest 332: <dfn id="task-queues">task queues</dfn>,
1.203 avankest 333: <dfn id="url">URL</dfn>,
1.232 avankest 334: <dfn id="url-character-encoding">URL character encoding</dfn>,
335: <dfn id="queue-a-task">queue a task</dfn>, and
336: <dfn id="valid-mime-type">valid MIME type</dfn>
1.250 avankest 337: are defined by the HTML5 specification.
1.157 avankest 338: [<cite><span>HTML5</span></cite>]</p>
1.210 avankest 339:
1.203 avankest 340: <p>The term <dfn id="entity-body">entity body</dfn> is used as described
341: in RFC 2616. <dfn id="method-token">Method token</dfn> is used as
342: described in section 5.1.1 of RFC 2616. <dfn><code>field-name</code></dfn>
343: and <dfn><code>field-value</code></dfn> are used as described in section
344: 4.2 of RFC 2616. [<cite><span>RFC2616</span></cite>]</p>
1.218 avankest 345:
1.258 avankest 346: <p>To <dfn>deflate a DOMString into a byte sequence</dfn> means to create
347: a sequence of bytes such that the <var title="">n</var>th byte of the
348: sequence is equal to the low-order byte of the <var title="">n</var>th
349: code point in the original DOMString.</p>
350:
351: <p>To <dfn>inflate a byte sequence into a DOMString</dfn> means to create
352: a DOMString such that the <var title="">n</var>th code point has 0x00 as
353: the high-order byte and the <var title="">n</var>th byte of the byte
354: sequence as the low-order byte.</p>
1.256 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: <p>In environments where the global object is represented by the
440: <code>Window</code> object the <code>XMLHttpRequest</code> object has an
441: associated
442: <dfn id="xmlhttprequest-document"><code>XMLHttpRequest</code> <code>Document</code></dfn>
443: which is the <code>Document</code> object associated with the
444: <code>Window</code> object for which the <code>XMLHttpRequest</code>
445: interface object was created.</p>
446:
447: <p class="note">The
448: <span><code>XMLHttpRequest</code> <code>Document</code></span> is used to
449: determine the <span><code>XMLHttpRequest</code> origin</span> and
450: <span><code>XMLHttpRequest</code> base URL</span> at a later stage.</p>
451:
452:
1.263 avankest 453:
1.203 avankest 454: <h3>Task Sources</h3>
1.218 avankest 455:
1.251 avankest 456: <p>The <span>task source</span> used by this specification is the
457: <dfn><code>XMLHttpRequest</code> task source</dfn>.</p>
1.203 avankest 458:
459:
1.211 avankest 460: <h3 id="constructors">Constructors</h3>
1.203 avankest 461:
1.263 avankest 462:
463:
1.203 avankest 464: <p>When the
1.266 avankest 465: <dfn id="dom-xmlhttprequest" title="dom-XMLHttpRequest"><code>XMLHttpRequest()</code></dfn>
1.203 avankest 466: constructor is invoked, the user agent <em class="ct">must</em> return a
467: new <code>XMLHttpRequest</code> object.</p>
468:
1.263 avankest 469:
1.203 avankest 470:
1.205 avankest 471: <h3 id="event-handler-attributes">Event Handler Attributes</h3>
472:
1.248 avankest 473:
474:
1.205 avankest 475: <p>The following is the
476: <span title="event handler attributes">event handler attribute</span> (and
477: its corresponding <span>event handler event type</span>) that
478: <em class="ct">must</em> be supported as DOM attribute by the
479: <code>XMLHttpRequest</code> object:</p>
480:
481: <table>
482: <thead>
483: <tr>
484: <th><span title="event handler attributes">event handler attribute</span>
485: <th><span>event handler event type</span>
486: <tbody>
487: <tr>
488: <td><dfn id="onreadystatechange"><code>onreadystatechange</code></dfn>
489: <td><code>readystatechange</code></td>
490: </table>
491:
492:
493: <h3 id="states">States</h3>
1.203 avankest 494:
495: <p>The <code>XMLHttpRequest</code> object can be in several states. The
496: <dfn id="readystate"><code>readyState</code></dfn> attribute, on getting,
497: <em class="ct">must</em> return the current state, which
498: <em class="ct">must</em> be one of the following values:</p>
499:
500: <dl>
501: <dt><dfn id="unsent-state" title="UNSENT state"><code>UNSENT</code></dfn>
502: (numeric value 0)</dt>
503: <dd><p>The object has been constructed.</p></dd>
504:
505: <dt><dfn id="opened-state" title="OPENED state"><code>OPENED</code></dfn>
506: (numeric value 1)</dt>
507: <dd><p>The <code>open()</code> method has been successfully invoked.
508: During this state request headers can be set using
509: <code>setRequestHeader()</code> and the request can be made using the
510: <code>send()</code> method.</p></dd>
511:
512: <dt><dfn id="headers-received-state" title="HEADERS_RECEIVED state"><code>HEADERS_RECEIVED</code></dfn>
513: (numeric value 2)</dt>
1.257 avankest 514: <dd><p>All redirects (if any) have been followed and all HTTP headers of
515: the final response have been received. Several response members of the
516: object are now available.</p></dd>
1.203 avankest 517:
518: <dt><dfn id="loading-state" title="LOADING state"><code>LOADING</code></dfn>
519: (numeric value 3)</dt>
520: <dd><p>The <span>response entity body</span> is being received.</p></dd>
521:
522: <dt><dfn id="done-state" title="DONE state"><code>DONE</code></dfn>
523: (numeric value 4)</dt>
524: <dd><p>The data transfer has been completed or something went wrong
525: during the transfer (e.g. infinite redirects).</p></dd>
526: </dl>
527:
528: <p>The <span title="OPENED state">OPENED</span> state has an associated
529: <dfn id="send-flag"><code>send()</code> flag</dfn> that indicates whether
530: the <code>send()</code> method has been invoked. It can be either true
531: or false and has an initial value of false.</p>
532:
533: <p>The <span title="DONE state">DONE</span> state has an associated
534: <dfn id="error-flag">error flag</dfn> that indicates some type of network
535: error or abortion. It can be either true or false and has an initial value
536: of false.</p>
537:
538:
1.205 avankest 539: <h3 id="request">Request</h3>
1.203 avankest 540:
541: <p>The <code>XMLHttpRequest</code> object holds the following request
542: metadata variables:</p>
543:
1.204 avankest 544: <dl>
545: <dt>The <dfn>asynchronous flag</dfn></dt>
1.266 avankest 546: <dd>True when <span title="fetch">fetching</span> is done asychronously.
547: False when fetching is done synchronously.</dd>
1.204 avankest 548:
549: <dt>The <dfn>request method</dfn></dt>
550: <dd>The method used in the request.</dd>
551:
552: <dt>The <dfn>request URL</dfn></dt>
553: <dd>The <span>URL</span> used in the request.</dd>
1.218 avankest 554:
1.204 avankest 555: <dt>The <dfn>request username</dfn></dt>
556: <dd>The username used in the request or null if there is no
557: username.</dd>
1.218 avankest 558:
1.204 avankest 559: <dt>The <dfn>request password</dfn></dt>
560: <dd>The password used in the request or null if there is no
561: password.</dd>
1.218 avankest 562:
1.204 avankest 563: <dt>The <dfn id="author-request-headers">author request headers</dfn></dt>
564: <dd>A list consisting of HTTP header name/value pairs to be used in the
565: request.</p>
1.203 avankest 566:
1.204 avankest 567: <dt>The <dfn>request entity body</dfn></dt>
1.218 avankest 568: <dd>The <span>entity body</span> used in the request.</dd>
1.248 avankest 569:
570:
1.204 avankest 571: </dl>
1.203 avankest 572:
1.248 avankest 573:
574:
1.203 avankest 575:
576: <h4>The <code title="">open()</code> method</h4>
1.88 avankest 577:
1.203 avankest 578: <p>When the <dfn id="open" title="open"><code>open(<var>method</var>,
579: <var title="">url</var>, <var>async</var>, <var>user</var>,
580: <var>password</var>)</code></dfn> method is invoked, the user agent
1.217 avankest 581: <em class="ct">must</em> run these steps (unless otherwise indicated):</p>
1.90 avankest 582:
1.88 avankest 583: <ol>
1.203 avankest 584: <li>
585: <p>If the <code>XMLHttpRequest</code> object has an associated
586: <span><code>XMLHttpRequest</code> <code>Document</code></span> run
587: these substeps:</p>
1.90 avankest 588:
1.203 avankest 589: <ol>
590: <li><p>If the
591: <span><code>XMLHttpRequest</code> <code>Document</code></span> is not
592: <span>fully active</span> raise an <code>INVALID_STATE_ERR</code>
593: exception and terminate the overall set of steps.</p></li>
594:
595: <li><p>Let <span><code>XMLHttpRequest</code> base URL</span> be the
596: <span>document base URL</span> of the
597: <span><code>XMLHttpRequest</code> <code>Document</code></span>.</p></li>
598:
599: <li><p>Let <span><code>XMLHttpRequest</code> origin</span> be the
600: <span>origin</span> of the
601: <span><code>XMLHttpRequest</code> <code>Document</code></span>.</p></li>
602: </ol>
603: </li>
1.90 avankest 604:
1.256 avankest 605: <li><p>If any code point in <var>method</var> is higher than
606: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS or after
607: <span title="deflate a DOMString into an byte sequence">deflating</span>
608: <var>method</var> it does not match the
1.210 avankest 609: <span>Method token</span> production raise a <code>SYNTAX_ERR</code>
1.256 avankest 610: exception and terminate these steps. Otherwise let <var>method</var> be
611: the result of
612: <span title="deflate a DOMString into an byte sequence">deflating</span>
613: <var>method</var>.</p></li> <!-- This sounds lame, but it works. -->
1.118 avankest 614:
1.115 avankest 615: <li>
1.256 avankest 616: <p>If <var>method</var> is a case-insensitive match for
1.203 avankest 617: <code>CONNECT</code>, <code>DELETE</code>, <code>GET</code>,
618: <code>HEAD</code>, <code>OPTIONS</code>, <code>POST</code>,
619: <code>PUT</code>, <code>TRACE</code>, or <code>TRACK</code>
1.256 avankest 620: subtract 0x20 from each byte in the range 0x61 (ASCII a) to
621: 0x7A (ASCII z).</p>
1.118 avankest 622:
1.203 avankest 623: <p class="note">If it does not match any of the above, it is passed
624: through <em>literally</em>, including in the final request.</p>
1.115 avankest 625: </li>
1.203 avankest 626: <!-- WebKit (and supposedly Gecko) also uppercase: COPY, INDEX, LOCK,
627: M-POST, MKCOL, MOVE, PROPFIND, PROPPATCH, and UNLOCK. -->
1.118 avankest 628:
1.111 avankest 629: <li>
1.256 avankest 630: <p>If <var>method</var> is a case-sensitive match for
1.259 avankest 631: <code>CONNECT</code>, <code>TRACE</code>, or <code>TRACK</code> raise a
632: <code>SECURITY_ERR</code> exception and terminate these steps.</p>
1.117 avankest 633:
1.203 avankest 634: <p class="note">Allowing these methods poses a security risk.
635: [<cite><span>HTTPVERBSEC</span></cite>]</p>
1.111 avankest 636: </li>
637:
1.203 avankest 638: <li><p>Let <var title="">url</var> be a <span>URL</span>.</p></li>
639:
1.209 avankest 640: <li><p>Let <span>URL character encoding</span> of <var title="">url</var>
641: be UTF-8.</p></li>
1.113 avankest 642:
1.255 avankest 643: <li><p><span title="Resolve a URL">Resolve</span> <var title="">url</var>
1.203 avankest 644: relative to the <span><code>XMLHttpRequest</code> base URL</span>.
645: If the algorithm returns an error raise a <code>SYNTAX_ERR</code>
646: exception and terminate these steps.</p></li>
647:
648: <!-- Presto and Gecko override the encoding. WebKit does not. Trident
649: does not support non-ASCII URLs. This matters for the <query> component,
650: see HTML5. -->
651:
652: <li><p>Drop <code><fragment></code> from <var title="">url</var>.</p></li>
653:
654: <li><p>If <var title="">url</var> contains an unsupported <code><scheme></code>
655: raise a <code>NOT_SUPPORTED_ERR</code> and terminate these
656: steps.</p></li>
657:
658: <li><p>If the <code>"user:password"</code> format in the
659: <code>userinfo</code> production is not supported for the relevant scheme
660: and <var title="">url</var> contains this format raise a
661: <code>SYNTAX_ERR</code> and terminate these steps.</p></li>
662:
663: <li><p>If <var title="">url</var> contains the <code>"user:password"</code>
664: format let <var>temp user</var> be the user part and
665: <var>temp password</var> be the password part.</p></li>
666:
667: <li><p>If <var title="">url</var> just contains the <code>"user"</code>
668: format let <var>temp user</var> be the user part.</p></li>
669:
1.248 avankest 670:
1.203 avankest 671: <li><p>If the <span>origin</span> of <var title="">url</var> is not
672: <span>same origin</span> with the
1.259 avankest 673: <span><code>XMLHttpRequest</code> origin</span> raise a
674: <code>SECURITY_ERR</code> exception and terminate these steps.</p></li>
1.248 avankest 675:
676:
1.203 avankest 677:
1.211 avankest 678: <li><p>Let <var>async</var> be the value of the <var>async</var> argument
1.266 avankest 679: or true if it was omitted.</p></li>
1.203 avankest 680:
681: <li>
682: <p>If the <var>user</var> argument was not omitted follow these sub
683: steps:</p>
1.90 avankest 684:
1.203 avankest 685: <ol>
1.263 avankest 686:
687:
1.203 avankest 688: <li><p>If the syntax of <var>user</var> does not match the syntax
689: specified by the relevant authentication scheme, raise a
690: <code>SYNTAX_ERR</code> exception and terminate the overall set of
691: steps.</p></li>
1.163 avankest 692:
1.239 avankest 693: <li><p>If <var>user</var> is null let <var>temp user</var>
1.203 avankest 694: be null.</p></li>
1.90 avankest 695:
1.203 avankest 696: <li><p>Otherwise let <var>temp user</var> be <var>user</var>.</p></li>
697: </ol>
1.88 avankest 698:
1.203 avankest 699: <p class="note">These steps override anything that may have been set by
700: the <var title="">url</var> argument.</p>
701: </li>
1.88 avankest 702:
1.128 avankest 703: <li>
1.203 avankest 704: <p>If the <var>password</var> argument was not omitted follow these sub
705: steps:</p>
706:
707: <ol>
1.263 avankest 708:
709:
1.203 avankest 710: <li><p>If the syntax of <var>password</var> does not match the syntax
711: specified by the relevant authentication scheme, raise a
712: <code>SYNTAX_ERR</code> exception and terminate the overall set of
713: steps.</p></li>
1.167 avankest 714:
1.239 avankest 715: <li><p>If <var>password</var> is null let
1.203 avankest 716: <var>temp password</var> be null.</p></li>
717:
718: <li><p>Otherwise let <var>temp password</var> be
719: <var>password</var>.</p></li>
720: </ol>
721:
722: <p class="note">These steps override anything that may have been set by
723: the <var title="">url</var> argument.</p>
1.128 avankest 724: </li>
1.88 avankest 725:
1.203 avankest 726: <li><p><span title="abort send()">Abort the <code>send()</code> algorithm</span>.</p></li>
727:
728: <li><p>The user agent <em class="ct">should</em> cancel any network
729: activity for which the object is responsible.</p></li>
730: <!-- we can hardly require it... -->
731:
1.252 avankest 732: <li><p>If there are any <span title="task">tasks</span> from the object's
733: <span><code>XMLHttpRequest</code> task source</span> in one of the
734: <span>task queues</span>, then remove those tasks.</p></li>
735:
1.203 avankest 736: <li>
737: <p>Set variables associated with the object as follows:</p>
738:
739: <ul>
740: <li><p>Set the <span><code>send()</code> flag</span> to false.</p></li>
741:
742: <li><p>Set <span>response entity body</span> to null.</p></li>
743:
744: <li><p>Empty the list of <span>author request headers</span>.</p>
745:
746: <li><p>Set the <span>request method</span> to <var>method</var>.</p></li>
747:
748: <li><p>Set the <span>request URL</span> to <var title="">url</var>.</p></li>
1.58 avankest 749:
1.203 avankest 750: <li><p>Set the <span>request username</span> to <var>temp user</var>.</p></li>
1.12 avankest 751:
1.203 avankest 752: <li><p>Set the <span>request password</span> to <var>temp password</var>.</p></li>
1.12 avankest 753:
1.266 avankest 754: <li><p>Set the <span>asynchronous flag</span> to the value of
755: <var>async</var>.</p></li>
1.203 avankest 756: </ul>
757: </li>
1.58 avankest 758:
1.203 avankest 759: <li><p>Switch the the state to
760: <span title="OPENED state">OPENED</span>.</p></li>
1.58 avankest 761:
1.203 avankest 762: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
763: </ol>
1.248 avankest 764:
765:
1.203 avankest 766: <p class="note">A future version or extension of this specification will
767: define a way of doing cross-origin requests.</p>
1.248 avankest 768:
1.58 avankest 769:
1.14 avankest 770:
1.203 avankest 771: <h4>The <code title="">setRequestHeader()</code> method</h4>
1.12 avankest 772:
1.235 avankest 773: <!-- XXX domintro authors
1.203 avankest 774: The <code>setRequestHeader()</code> method can be used to set new request
1.184 avankest 775: headers and append to request headers already in the list.</p>
1.203 avankest 776: -->
1.45 avankest 777:
1.203 avankest 778: <p>As indicated in the algorithm below certain headers cannot be set and
779: are left up to the user agent. In addition there are certain other headers
780: the user agent will take control of if they are not set by the author as
781: indicated at the end of the <code>send()</code> method section.</p>
782:
783: <p class="note">The <code>setRequestHeader()</code> method appends a
784: value if the HTTP header given as argument is already part of the
785: <span>author request headers</span> list.</p>
786:
1.248 avankest 787:
788:
1.203 avankest 789: <p>When the
790: <dfn id="setrequestheader" title="setrequestheader"><code>setRequestHeader(<var>header</var>,
791: <var>value</var>)</code></dfn> method is invoked, the user agent
1.259 avankest 792: <em class="ct">must</em> run these steps:</p>
1.14 avankest 793:
1.203 avankest 794: <ol>
795: <li><p>If the state is not <span title="OPENED state">OPENED</span> raise
796: an <code>INVALID_STATE_ERR</code> exception and terminate these
797: steps.</p></li>
798:
799: <li><p>If the <span><code>send()</code> flag</span> is true raise an
800: <code>INVALID_STATE_ERR</code> exception and terminate these
801: steps.</p></li>
802:
1.256 avankest 803: <li><p>If any code point in <var>header</var> is higher than
804: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS or after
805: <span title="deflate a DOMString into an byte sequence">deflating</span>
806: <var>header</var> it does not match the
807: <span>field-name</span> production raise a <code>SYNTAX_ERR</code>
808: exception and terminate these steps. Otherwise let <var>header</var> be
809: the result of
810: <span title="deflate a DOMString into an byte sequence">deflating</span>
811: <var>header</var>.</p></li> <!-- This sounds lame, but it works. -->
1.203 avankest 812:
813: <li>
1.256 avankest 814: <p>If any code point in <var>value</var> is higher than
815: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS or after
816: <span title="deflate a DOMString into an byte sequence">deflating</span>
817: <var>value</var> it does not match the
818: <span>field-value</span> production raise a <code>SYNTAX_ERR</code>
819: exception and terminate these steps. Otherwise let <var>value</var> be
820: the result of
821: <span title="deflate a DOMString into an byte sequence">deflating</span>
822: <var>value</var>.</p> <!-- This sounds lame, but it works. -->
1.203 avankest 823:
824: <p class="note">The empty string is legal and represents the empty
825: header value.</p>
826: </li>
827:
828: <li>
1.259 avankest 829: <p>Terminate these steps if <var>header</var> is a case-insensitive
830: match for one of the following headers:</p>
1.203 avankest 831:
832: <ul>
833: <li><code>Accept-Charset</code></li>
834: <li><code>Accept-Encoding</code></li>
835: <li><code>Connection</code></li>
836: <li><code>Content-Length</code></li>
837: <li><code>Cookie</code></li>
838: <li><code>Cookie2</code></li>
839: <li><code>Content-Transfer-Encoding</code></li>
840: <li><code>Date</code></li>
841: <li><code>Expect</code></li>
842: <li><code>Host</code></li>
843: <li><code>Keep-Alive</code></li>
844: <li><code>Referer</code></li>
845: <li><code>TE</code></li>
846: <li><code>Trailer</code></li>
847: <li><code>Transfer-Encoding</code></li>
848: <li><code>Upgrade</code></li>
849: <li><code>User-Agent</code></li>
850: <li><code>Via</code></li>
851: </ul>
1.96 avankest 852:
1.256 avankest 853: <p>… or if the start of <var>header</var> is a case-insensitive
854: match for <code>Proxy-</code> or <code>Sec-</code> (including when
855: <var>header</var> is just <code>Proxy-</code> or <code>Sec-</code>).</p>
1.203 avankest 856:
857: <p class="note">The above headers are not allowed to be set as they are
858: better controlled by the user agent as it knows best what value they
1.259 avankest 859: ought to have. Header names starting with <code>Sec-</code> are not
1.203 avankest 860: allowed to be set to allow new headers to be minted in the future that
861: are guaranteed not to come from <code>XMLHttpRequest</code>. (Older
862: clients would however still be vulnerable as they allow such headers to
863: be set.)</p>
864: </li>
1.14 avankest 865:
1.203 avankest 866: <li><p>If <var>header</var> is not in the
867: <span>author request headers</span> list append <var>header</var> with
868: its associated <var>value</var> to the list and terminate these
869: steps.</p></li>
870:
871: <li><p>If <var>header</var> is in the <span>author request headers</span>
872: list either use multiple headers, combine the values or use a combination
873: of those (section 4.2, RFC 2616).
874: [<cite><span>RFC2616</span></cite>]</p></li>
875: <!-- XXX it seems UAs always combine the values -->
876: </ol>
1.45 avankest 877:
1.203 avankest 878: <p class="note">See also the <code>send()</code> method regarding user
879: agent header handling for caching, authentication, proxies, and
880: cookies.</p>
1.14 avankest 881:
1.203 avankest 882: <div class="example">
883: <pre><code>// The following script:
1.14 avankest 884: var client = new XMLHttpRequest();
885: client.open('GET', 'demo.cgi');
886: client.setRequestHeader('X-Test', 'one');
887: client.setRequestHeader('X-Test', 'two');
888: client.send();
889:
890: // ...would result in the following header being sent:
891: ...
892: X-Test: one, two
1.58 avankest 893: ...</code></pre>
1.203 avankest 894: </div>
1.255 avankest 895:
1.248 avankest 896:
1.218 avankest 897:
1.203 avankest 898:
899: <h4>The <code title="">send()</code> method</h4>
1.12 avankest 900:
1.235 avankest 901: <!-- XXX domintro
1.203 avankest 902: <p>The <code>send()</code> method initiates the request and its optional
1.204 avankest 903: argument provides the <span>request entity body</span>.</p>
1.235 avankest 904: -->
1.203 avankest 905:
906: <p>When the
907: <dfn id="send" title="send"><code>send(<var>data</var>)</code></dfn>
908: method is invoked, the user agent <em class="ct">must</em> run the
909: following steps (unless otherwise noted). This algorithm gets aborted when
910: the <code>open()</code> or <code>abort()</code> method is invoked. When
911: the
912: <dfn title="abort send()" id="abort-send-algorithm"><code>send()</code> algorithm is aborted</dfn>
913: the user agent <em class="ct">must</em> terminate the algorithm after
914: finishing the step it is on.</p>
915:
916: <p class="note">The <code title="">send()</code> algorithm can only be
917: aborted when the <span>asynchronous flag</span> is true and only after the
918: method call has returned.</p>
1.181 avankest 919:
1.203 avankest 920: <ol>
921: <li><p>If the state is not <span title="OPENED state">OPENED</span> raise
922: an <code>INVALID_STATE_ERR</code> exception and terminate these
923: steps.</p></li>
924:
925: <li><p>If the <span><code>send()</code> flag</span> is true raise an
926: <code>INVALID_STATE_ERR</code> exception and terminate these
927: steps.</p></li>
1.58 avankest 928:
1.203 avankest 929: <li>
930: <p>If the <span>request method</var> is <code>GET</code> or
1.239 avankest 931: <code>HEAD</code> act as if <var>data</var> is null.</p>
1.232 avankest 932:
933: <p>If the <var>data</var> argument has been omitted or is
1.239 avankest 934: null, do not include a <span>request entity body</span>
1.232 avankest 935: and go to the next step.</p>
1.248 avankest 936:
937: <p>Otherwise, let <var>encoding</var> be null, <var>mime type</var> be
938: null, and then follow these rules:</p>
1.203 avankest 939:
940: <dl class="switch">
1.248 avankest 941:
942:
943: <dt>If <var>data</var> is a <code>Document</code>
1.203 avankest 944:
945: <dd>
1.232 avankest 946: <p>Let <var>encoding</var> be the <span>preferred MIME name</span> of
947: the
948: <span title="document's character encoding">character encoding</span>
949: of <var>data</var>. If <var>encoding</var> is UTF-16 change it to
950: UTF-8.</p>
951:
1.248 avankest 952: <p>Let <var>mime type</var> be "<code>application/xml;charset=</code>"
953: followed by <var>encoding</var>.</p>
1.232 avankest 954:
955: <p>Let the <span>request entity body</span> be the result of getting
956: the <code title="dom-innerHTML">innerHTML</code> attribute on
1.233 avankest 957: <var>data</var>
958: <span title="convert a DOMString to a sequence of Unicode characters">converted to Unicode</span>
959: and encoded as <var>encoding</var>. Re-raise any exception this
960: raises.</p>
1.218 avankest 961:
1.233 avankest 962: <p class="note">In particular, if the document cannot be serialized an
1.217 avankest 963: <code>INVALID_STATE_ERR</code> exception is raised.</p>
964:
1.203 avankest 965: <p class="note">Subsequent changes to the <code>Document</code> have
966: no effect on what is submitted.</p>
967: </dd>
1.237 avankest 968:
1.248 avankest 969: <dt>If <var>data</var> is a <code>DOMString</code></dt>
1.237 avankest 970:
1.248 avankest 971: <dd>
972: <p>Let <var>encoding</var> be UTF-8.</p>
973:
974: <p>Let <var>mime type</var> be "<code>text/plain;charset=UTF-8</code>".</p>
975:
976: <p>Let the <span>request entity body</span> be <var>data</var>
977: <span title="convert a DOMString to a sequence of Unicode characters">converted to Unicode</span>
978: and encoded as UTF-8.</p>
979: </dd>
980:
981:
1.203 avankest 982: </dl>
1.58 avankest 983:
1.232 avankest 984: <p>If a <code>Content-Type</code> header is set using
1.248 avankest 985: <code>setRequestHeader()</code> whose value is a
986: <span>valid MIME type</span> and has a <code>charset</code>
1.256 avankest 987: parameter whose value is not a case-insensitive match for
988: <var>encoding</var>, and <var>encoding</var> is not null, set all the
989: <code>charset</code> parameters of the <code>Content-Type</code> header
990: to <var>encoding</var>.</p>
1.232 avankest 991:
992: <p>If no <code>Content-Type</code> header has been set using
1.248 avankest 993: <code>setRequestHeader()</code> and <var>mime type</var> is not null set
994: a <code>Content-Type</code> request header with as value
995: <var>mime type</var>.</p>
1.236 avankest 996:
997: <!-- reminder: if we ever change this to always include charset it has
998: to be included as the first parameter for compatibility reasons -->
1.203 avankest 999: </li>
1.202 avankest 1000:
1.203 avankest 1001: <li><p>If the <span>asynchronous flag</span> is false release the
1002: <span>storage mutex</span>.</p></li>
1.103 avankest 1003:
1.248 avankest 1004:
1005:
1.203 avankest 1006: <li><p>Set the <span>error flag</span> to false.</p></li>
1.218 avankest 1007:
1.248 avankest 1008:
1009:
1.211 avankest 1010: <li>
1011: <p>If the <span>asynchronous flag</span> is true run these substeps:</p>
1.218 avankest 1012:
1.211 avankest 1013: <ol>
1.217 avankest 1014: <li><p>Set the <span><code>send()</code> flag</span> to true.</p></li>
1015:
1.211 avankest 1016: <li>
1017: <p><span>Dispatch a <code>readystatechange</code> event</span>.</p>
1.145 avankest 1018:
1.211 avankest 1019: <p class="note">The state does not change. The event is dispatched for
1020: historical reasons.</p>
1021: </li>
1022:
1.248 avankest 1023:
1024:
1.211 avankest 1025: <li><p>Return the <code>send()</code> method call, but continue running
1026: the steps in this algorithm.</p></li>
1027: </ol>
1028: </li>
1.218 avankest 1029:
1.203 avankest 1030: <li>
1.248 avankest 1031:
1.211 avankest 1032:
1.261 avankest 1033: <p><span>Fetch</span> the <span>request URL</span> from
1.260 avankest 1034: <i title="">origin</i>
1035: <span><code>XMLHttpRequest</code> origin</span>, with the
1036: <i title="">synchronous flag</i> set if the
1037: <span>asynchronous flag</span> is false, using HTTP method
1.248 avankest 1038: <span>request method</span>, user <span>request username</span> (if
1039: non-null) and password <span>request password</span> (if non-null),
1040: taking into account the <span>request entity body</span>, list of
1041: <span>author request headers</span> and the rules listed at the end of
1042: this section.</p>
1043:
1044: <dl class="switch">
1045: <dt>If the <span>asynchronous flag</span> is false</dt>
1046: <dd>
1047: <p>While making the request also follow the
1048: <span>same-origin request event rules</span>.</p>
1049:
1050: <!--
1051: This cannot involve any task queue whatsoever because that would
1052: mean other tasks on the task queue might get processed as well
1053: which is counter to the whole idea of doing things synchronous.
1054: -->
1055:
1056: <p class="note">The <code>send()</code> method call will now be
1057: returned by virtue of this algorithm ending.</p>
1058: </dd>
1059:
1060: <dt>If the <span>asynchronous flag</span> is true</dt>
1061: <dd>
1062: <p><span>Make progress notifications</span>.</p>
1063:
1064: <p><span>Make upload progress notifications</span>.</p>
1065:
1066: <p>While processing the request, as data becomes available and when
1067: the user interferes with the request,
1.255 avankest 1068: <span title="queue a task">queue tasks</span> to update the
1069: <span>response entity body</span> and follow the
1.254 avankest 1070: <span>same-origin request event rules</span>.</p>
1.248 avankest 1071: </dd>
1072: </dl>
1073:
1.203 avankest 1074: </li>
1075: </ol>
1.60 avankest 1076:
1.203 avankest 1077: <hr>
1078:
1.227 avankest 1079: <p>If the user agent allows the end user to configure a proxy it
1.248 avankest 1080: <em class="ct">should</em> modify the request appropriately; i.e., connect
1081: to the proxy host instead of the origin server, modify the
1082: <code>Request-Line</code> and send <code>Proxy-Authorization</code>
1083: headers as specified.</p>
1.262 avankest 1084:
1085: <hr>
1.212 avankest 1086:
1.218 avankest 1087: <p>If the user agent supports HTTP Authentication and
1.262 avankest 1088: <code title="http-authorization">Authorization</code> is not in the list
1089: of <span>author request headers</span>, it <em class="ct">should</em>
1.218 avankest 1090: consider requests originating from the <code>XMLHttpRequest</code> object
1091: to be part of the protection space that includes the accessed URIs and
1.262 avankest 1092: send <code title="http-authorization">Authorization</code> headers and
1093: handle <code>401 Unauthorized</code> requests appropriately.</p>
1094:
1095: <p>If authentication fails,
1096: <code title="http-authorization">Authorization</code> is not in the list
1097: of <span>author request headers</span>, <span>request username</span> is
1098: null, and <span>request password</span> is null, user agents
1099: <em class="ct">should</em> prompt the end user for their username and
1100: password.</p>
1101:
1102: <p>If authentication fails,
1103: <code title="http-authorization">Authorization</code> is not in the list
1104: of <span>author request headers</span>, <span>request username</span> is
1105: non-null, and <span>request password</span> is non-null, user agents
1106: <em class="ct">must not</em> prompt the end user for their username and
1107: password. [<cite><span>RFC2617</span></cite>]</p>
1.212 avankest 1108:
1.266 avankest 1109: <p class="note">End users are not prompted if username/password are
1110: provided through the <code>open()</code> API so that authors can implement
1111: their own user interface.</p>
1.262 avankest 1112:
1113: <hr>
1.212 avankest 1114:
1115: <p>If the user agent supports HTTP State Management it
1116: <em class="ct">should</em> persist, discard and send cookies (as received
1117: in the <code>Set-Cookie</code> and <code>Set-Cookie2</code> response
1118: headers, and sent in the <code>Cookie</code> header) as applicable.
1119: [<cite><span>COOKIES</span></cite>]</p>
1.262 avankest 1120:
1121: <hr>
1.212 avankest 1122:
1123: <p>If the user agent implements a HTTP cache it <em class="ct">should</em>
1.248 avankest 1124: respect <code>Cache-Control</code> request headers set by the
1125: <code>setRequestHeader()</code> (e.g., <code>Cache-Control:
1126: no-cache</code> bypasses the cache). It <em class="ct">must not</em> send
1.212 avankest 1127: <code>Cache-Control</code> or <code>Pragma</code> request headers
1.227 avankest 1128: automatically unless the end user explicitly requests such behavior
1.212 avankest 1129: (e.g. by (force-)reloading the page).</p>
1130:
1131: <p>For <code>304 Not Modified</code> responses that are a result of a
1132: user agent generated conditional request the user agent
1133: <em class="ct">must</em> act as if the server gave a <code>200 OK</code>
1134: response with the appropriate content. The user agent
1135: <em class="ct">must</em> allow <code>setRequestHeader()</code> to
1.248 avankest 1136: override automatic cache validation by setting request headers (e.g.
1137: <code>If-None-Match</code> or <code>If-Modified-Since</code>), in which
1.212 avankest 1138: case <code>304 Not Modified</code> responses <em class="ct">must</em> be
1139: passed through. [<cite><span>RFC2616</span></cite>]</p>
1.262 avankest 1140:
1141: <hr>
1.212 avankest 1142:
1143: <p>If the user agent implements server-driven content-negotiation
1144: it <em class="ct">should</em> set <code>Accept-Encoding</code> and
1.231 avankest 1145: <code>Accept-Charset</code> headers as appropriate. For
1146: <code>Accept</code> and <code>Accept-Language</code> the user agent
1147: <em class="ct">must</em> follow these constraints:</p>
1148:
1149: <ul>
1150: <li><p>Both headers <em class="ct">must not</em> be modified if they are
1151: already set through <code>setRequestHeader()</code>.</p></li>
1.255 avankest 1152:
1.231 avankest 1153: <li><p>If not set through <code>setRequestHeader()</code>
1.255 avankest 1154: <code>Accept-Language</code> <em class="ct">should</em> be set as
1.231 avankest 1155: appropriate.</p></li>
1156:
1157: <li><p>If not set through <code>setRequestHeader()</code>
1158: <code>Accept</code> <em class="ct">must</em> be set with as value
1159: <code>*/*</code>.</p></li>
1160: </ul>
1161:
1162: <p>Responses <em class="ct">must</em> have the content-encodings
1163: automatically decoded. [<cite><span>RFC2616</span></cite>]</p>
1.212 avankest 1164:
1.262 avankest 1165: <hr>
1166:
1.212 avankest 1167: <p>Besides the <span>author request headers</span> user agents
1168: <em class="ct">should not</em> include additional request headers other
1.248 avankest 1169: than those mentioned above or other than those authors are not allowed to
1170: set using <code>setRequestHeader()</code>. This ensures that authors have
1171: a reasonably predictable API.</p>
1.218 avankest 1172:
1.212 avankest 1173:
1174: <h4>Infrastructure for the <code title="">send()</code> method</h4>
1.216 avankest 1175:
1.219 avankest 1176: <p>The <dfn>same-origin request event rules</dfn> are as follows:</p>
1.118 avankest 1177:
1.203 avankest 1178: <dl class="switch">
1179: <dt>If the response is an HTTP redirect</dt>
1180: <dd>
1.248 avankest 1181:
1.257 avankest 1182: <p>If the <span>origin</span> of the <span>URL</span> conveyed by the
1183: <code title="http-location">Location</code> header is
1184: <span>same origin</span> with the
1185: <span><code>XMLHttpRequest</code> origin</span> and the redirect does
1186: not violate infinite loop precautions, transparently follow the redirect
1187: while observing the <span>same-origin request event rules</span>.</p>
1.248 avankest 1188:
1189: <p>Otherwise, this is a <span>network error</span>.</p>
1190:
1191:
1.203 avankest 1192:
1193: <p class="note">HTTP places requirements on the user agent regarding the
1.204 avankest 1194: preservation of the <span>request method</span> and
1.248 avankest 1195: <span>request entity body</span> during redirects, and also requires end
1196: users to be notified of certain kinds of automatic redirections.</p>
1.203 avankest 1197: <!-- XXX HTTP needs fixing here -->
1.213 avankest 1198: </dd>
1.121 avankest 1199:
1.227 avankest 1200: <dt>If the end user cancels the download</dt>
1.213 avankest 1201: <dd><p>This is an <span>abort error</span>.</p></dd>
1.60 avankest 1202:
1.214 avankest 1203: <dt>In case of network errors</dt>
1.213 avankest 1204: <dd>
1205: <p>In case of DNS errors, TLS negotiation failure, or other type of
1206: network errors, this is a <span>network error</span>. Do not request any
1.227 avankest 1207: kind of end user interaction.</p>
1.121 avankest 1208:
1.213 avankest 1209: <p class="note">This does not include HTTP responses that indicate
1210: some type of error, such as HTTP status code 410.</p>
1211: </dd>
1.60 avankest 1212:
1.248 avankest 1213:
1214:
1.213 avankest 1215: <dt>Once all HTTP headers have been received and the
1.257 avankest 1216: <span>asynchronous flag</span> is true (and this is not an HTTP
1217: redirect)</dt>
1.213 avankest 1218: <dd><p><span>Switch to the HEADERS_RECEIVED state</span>.</p></dd>
1.186 avankest 1219:
1.220 avankest 1220: <dt>Once the first byte (or more) of the
1221: <span>response entity body</span> has been received and the
1222: <span>asynchronous flag</span> is true</dt>
1223: <dt>If there is no <span>response entity body</span> and the
1.213 avankest 1224: <span>asynchronous flag</span> is true</dt>
1.215 avankest 1225: <dd><p><span>Switch to the LOADING state</span>.</p></dd>
1.220 avankest 1226:
1227: <dt>Once the whole <span>response entity body</span> has been
1228: received</dt>
1.224 avankest 1229: <dt>If there is no <span>response entity body</span> and the
1230: <span>asynchronous flag</span> is false or the state is
1.221 avankest 1231: <span title="LOADING state">LOADING</span></dt>
1.220 avankest 1232: <dd><p><span>Switch to the DONE state</span>.</p></dd>
1.213 avankest 1233: </dl>
1.218 avankest 1234:
1.248 avankest 1235:
1236:
1.213 avankest 1237: <hr>
1.218 avankest 1238:
1.241 avankest 1239: <p>When something is said to be a <dfn>network error</dfn> run the
1240: <span>request error</span> steps for exception
1241: <code>NETWORK_ERR</code>.</p>
1242:
1243: <p>When something is said to be an <dfn>abort error</dfn> run the
1244: <span>request error</span> steps for exception
1245: <code>ABORT_ERR</code>.</p>
1.60 avankest 1246:
1.248 avankest 1247:
1248:
1.242 avankest 1249: <p>When something is said to be a <dfn>request error</dfn> for
1.248 avankest 1250: exception <var>exception</var> run these
1251: steps:</p>
1.12 avankest 1252:
1.213 avankest 1253: <ol>
1.254 avankest 1254: <li><p>The user agent <em class="ct">should</em> cancel any network
1255: activity for which the object is responsible.</p></li>
1256:
1257: <li><p>If there are any <span title="task">tasks</span> from the object's
1258: <span><code>XMLHttpRequest</code> task source</span> in one of the
1259: <span>task queues</span>, then remove those tasks.</p></li>
1.250 avankest 1260:
1.213 avankest 1261: <li><p>Set the <span>response entity body</span> to null.</p></li>
1.203 avankest 1262:
1.254 avankest 1263: <li><p>Empty the list of <span>author request headers</span>.</p></li>
1264:
1.213 avankest 1265: <li><p>Set the the <span>error flag</span> to true.</p></li>
1.12 avankest 1266:
1.213 avankest 1267: <li><p>Switch the state to <span title="DONE state">DONE</span>.</p></li>
1.203 avankest 1268:
1.241 avankest 1269: <li><p>If the <span>asynchronous flag</span> is false raise an
1270: <var>exception</var> exception and terminate the overall set of
1.213 avankest 1271: steps.</p></li>
1.203 avankest 1272:
1.248 avankest 1273: <li>
1.249 avankest 1274: <p><span>Dispatch a <code>readystatechange</code> event</span>.</p>
1.248 avankest 1275:
1276: <p class="note">At this point it is clear that the
1277: <span>asynchronous flag</span> is true.</p>
1278: </li>
1279:
1280:
1.203 avankest 1281:
1.248 avankest 1282: <li><p>Terminate the overall algorithm.</p></li>
1.213 avankest 1283: </ol>
1.203 avankest 1284:
1.248 avankest 1285:
1286: <p class="note">A future version of this specification will dispatch an
1287: <code>error</code>/<code>abort</code> event here as well. (Depending on
1288: the type of error.)</p>
1289:
1.203 avankest 1290:
1.213 avankest 1291: <hr>
1.203 avankest 1292:
1.213 avankest 1293: <p>When it is said to
1294: <dfn id="switch-headers-received">switch to the HEADERS_RECEIVED state</dfn>
1295: run these steps:</p>
1.203 avankest 1296:
1.213 avankest 1297: <ol>
1298: <li><p>Switch the state to <span title="HEADERS_RECEIVED state">HEADERS_RECEIVED</span>.</p></li>
1.203 avankest 1299:
1.249 avankest 1300: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.213 avankest 1301: </ol>
1.218 avankest 1302:
1.213 avankest 1303: <p>When it is said to
1304: <dfn id="switch-loading">switch to the LOADING state</dfn> run these
1305: steps:</p>
1.218 avankest 1306:
1.213 avankest 1307: <ol>
1308: <li><p>Switch the state to <span title="LOADING state">LOADING</span>.</p></li>
1.203 avankest 1309:
1.249 avankest 1310: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.213 avankest 1311: </ol>
1.218 avankest 1312:
1.216 avankest 1313: <p>When it is said to
1314: <dfn id="switch-done">switch to the DONE state</dfn> run these steps:</p>
1.218 avankest 1315:
1.216 avankest 1316: <ol>
1.255 avankest 1317: <li><p>If the <span>asynchronous flag</span> is false update the
1318: <span>response entity body</span>.</p></li>
1319:
1.216 avankest 1320: <li><p>Switch the state to <span title="DONE state">DONE</span>.</p></li>
1321:
1.248 avankest 1322: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1323:
1.220 avankest 1324:
1.216 avankest 1325: </ol>
1.218 avankest 1326:
1.248 avankest 1327:
1328:
1.203 avankest 1329:
1330: <h4>The <code title="">abort()</code> method</h4>
1331:
1332: <p>When the <dfn id="abort"><code>abort()</code></dfn> method is invoked,
1.217 avankest 1333: the user agent <em class="ct">must</em> run these steps (unless otherwise
1334: noted):</p>
1.12 avankest 1335:
1.203 avankest 1336: <ol>
1337: <li><p><span title="abort send()">Abort the <code>send()</code> algorithm</span>.</p></li>
1338:
1339: <li><p>The user agent <em class="ct">should</em> cancel any network
1340: activity for which the object is responsible.</p></li>
1.252 avankest 1341:
1342: <li><p>If there are any <span title="task">tasks</span> from the object's
1343: <span><code>XMLHttpRequest</code> task source</span> in one of the
1344: <span>task queues</span>, then remove those tasks.</p></li>
1.203 avankest 1345:
1346: <li><p>Set the <span>response entity body</span> to null.</p></li>
1347:
1.252 avankest 1348: <li><p>Empty the list of <span>author request headers</span>.</p></li>
1349:
1.203 avankest 1350: <li><p>Set the <span>error flag</span> to true.</p></li>
1351:
1352: <li>
1353: <p>If the state is <span title="UNSENT state">UNSENT</span>,
1354: <span title="OPENED state">OPENED</span> with the
1355: <span><code>send()</code> flag</span> being false, or
1356: <span title="DONE state">DONE</span> go to the next step.</p>
1.12 avankest 1357:
1.203 avankest 1358: <p>Otherwise run these substeps:</p>
1.58 avankest 1359:
1360: <ol>
1.203 avankest 1361: <li><p>Switch the state to <span title="DONE state">DONE</span>.</p></li>
1.170 avankest 1362:
1.203 avankest 1363: <li><p>Set the <span><code>send()</code> flag</span> to false.</p></li>
1.96 avankest 1364:
1.203 avankest 1365: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.248 avankest 1366:
1367:
1.58 avankest 1368: </ol>
1.250 avankest 1369:
1.248 avankest 1370:
1.250 avankest 1371: <p class="note">A future version of this specification will dispatch an
1372: <code title="abort-event">abort</code> event here.</p>
1.248 avankest 1373:
1.203 avankest 1374: </li>
1375:
1376: <li>
1377: <p>Switch the state to <span title="UNSENT state">UNSENT</span>.</p>
1378:
1379: <p class="note">No <code>readystatechange</code> event is dispatched.</p>
1380: </li>
1381: </ol>
1382:
1383:
1384:
1.205 avankest 1385: <h3 id="response">Response</h3>
1.203 avankest 1386:
1387: <h4>The <code title="">status</code> attribute</h4>
1388:
1389: <p>The <dfn id="status"><code>status</code></dfn> attribute
1.222 avankest 1390: <em class="ct">must</em> return the result of running these steps:</p>
1.226 avankest 1391:
1.222 avankest 1392: <ol>
1393: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1394: <span title="OPENED state">OPENED</span> return 0 and terminate these
1.222 avankest 1395: steps.</p></li>
1396:
1.239 avankest 1397: <li><p>If the <span>error flag</span> is true return 0 and terminate
1398: these steps.</p></li>
1.222 avankest 1399:
1400: <li><p>Return the HTTP status code.</p></li>
1.248 avankest 1401: </ol>
1.203 avankest 1402:
1403:
1404: <h4>The <code title="">statusText</code> attribute</h4>
1405:
1406: <p>The <dfn id="statustext"><code>statusText</code></dfn> attribute
1.222 avankest 1407: <em class="ct">must</em> return the result of running these steps:</p>
1408:
1409: <ol>
1410: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1411: <span title="OPENED state">OPENED</span> return the empty string and
1412: terminate these steps.</p></li>
1.222 avankest 1413:
1414: <li><p>If the <span>error flag</span> is true return the empty string and
1415: terminate these steps.</p></li>
1416:
1417: <li><p>Return the HTTP status text.</p></li>
1418: </ol>
1.203 avankest 1419:
1420:
1421: <h4>The <code title="">getResponseHeader()</code> method</h4>
1422:
1423: <p>When the
1424: <dfn id="getresponseheader" title="getresponseheader"><code>getResponseHeader(<var>header</var>)</code></dfn>
1.217 avankest 1425: is invoked, the user agent <em class="ct">must</em> run these steps:</p>
1.203 avankest 1426:
1427: <ol>
1428: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1429: <span title="OPENED state">OPENED</span> return null and terminate these
1.203 avankest 1430: steps.</p></li>
1431:
1.239 avankest 1432: <li><p>If the <span>error flag</span> is true return null
1.203 avankest 1433: and terminate these steps.</p></li>
1434:
1.256 avankest 1435: <li><p>If any code point in <var>header</var> is higher than
1436: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS return null and terminate
1437: these steps.</p></li>
1438:
1439: <li><p>Let <var>header</var> be the result of
1440: <span title="deflate a DOMString into an byte sequence">deflating</span>
1441: <var>header</var>.</p></li> <!-- This sounds lame, but it works. -->
1442:
1443: <li><p>If <var>header</var> is a case-insensitive match for
1444: <code>Set-Cookie</code> or <code>Set-Cookie2</code> return null and
1445: terminate these steps.</p></li>
1.203 avankest 1446:
1.256 avankest 1447: <li><p>If <var>header</var> is a case-insensitive match for multiple HTTP
1448: response headers, return the
1449: <span title="inflate an byte sequence into a DOMString">inflated</span>
1450: values of these headers as a single concatenated string separated from
1451: each other by a U+002C COMMA U+0020 SPACE character pair and terminate
1452: these steps.</p></li>
1.203 avankest 1453:
1.256 avankest 1454: <li><p>If <var>header</var> is a case-insensitive match for a single HTTP
1455: response header, return the
1456: <span title="inflate an byte sequence into a DOMString">inflated</span>
1457: value of that header and terminate these steps.</p></li>
1.203 avankest 1458:
1.239 avankest 1459: <li><p>Return null.</p></li>
1.203 avankest 1460: </ol>
1461:
1.248 avankest 1462:
1463:
1.203 avankest 1464: <div class="example">
1.250 avankest 1465:
1466: <p>For the following script:</p>
1467:
1468: <pre><code>var client = new XMLHttpRequest();
1469: client.open("GET", "unicorns-are-teh-awesome.txt", true);
1.5 avankest 1470: client.send();
1.12 avankest 1471: client.onreadystatechange = function() {
1.250 avankest 1472: if(this.readyState == 2) {
1473: print(client.getResponseHeader("Content-Type"));
1474: }
1475: }</code></pre>
1476:
1477: <p>The <code>print()</code> function will get to process something
1478: like:</p>
1.5 avankest 1479:
1.250 avankest 1480: <pre><code>text/plain; charset=UTF-8</code></pre>
1.203 avankest 1481: </div>
1.12 avankest 1482:
1483:
1.203 avankest 1484: <h4>The <code title="">getAllResponseHeaders()</code> method</h4>
1.14 avankest 1485:
1.203 avankest 1486: <p>When the
1487: <dfn id="getallresponseheaders"><code>getAllResponseHeaders()</code></dfn>
1488: method is invoked, the user agent <em class="ct">must</em> run the
1489: following steps:</p>
1.58 avankest 1490:
1.203 avankest 1491: <ol>
1492: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1493: <span title="OPENED state">OPENED</span> return the empty string and
1494: terminate these steps.</p></li>
1.203 avankest 1495:
1496: <li><p>If the <span>error flag</span> is true return the empty string and
1497: terminate these steps.</p></li>
1498:
1.256 avankest 1499: <li><p>Return all the HTTP headers, excluding headers that are a
1500: case-insensitive match for <code>Set-Cookie</code> or
1501: <code>Set-Cookie2</code>,
1502: <span title="inflate an byte sequence into a DOMString">inflated</span>,
1503: as a single string, with each header line
1504: separated by a U+000D CR U+000A LF pair, excluding the status line, and
1.203 avankest 1505: with each header name and header value separated by a
1506: U+003A COLON U+0020 SPACE pair.</p></li>
1507: </ol>
1.58 avankest 1508:
1.250 avankest 1509:
1510:
1.203 avankest 1511: <div class="example">
1.250 avankest 1512: <p>For the following script:</p>
1513:
1514: <pre><code>var client = new XMLHttpRequest();
1515: client.open("GET", "narwhals-too.txt", true);
1.5 avankest 1516: client.send();
1.12 avankest 1517: client.onreadystatechange = function() {
1.179 avankest 1518: if(this.readyState == 2) {
1.203 avankest 1519: print(this.getAllResponseHeaders());
1.12 avankest 1520: }
1.250 avankest 1521: }</code></pre>
1522:
1523: <p>The <code>print()</code> function will get to process something
1524: like:</p>
1.1 avankest 1525:
1.250 avankest 1526: <pre><code>Date: 2004年10月24日 04:58:38 GMT
1.203 avankest 1527: Server: Apache/1.3.31 (Unix)
1528: Keep-Alive: timeout=15, max=99
1529: Connection: Keep-Alive
1530: Transfer-Encoding: chunked
1531: Content-Type: text/plain; charset=utf-8</code></pre>
1532: </div>
1533:
1.250 avankest 1534:
1.203 avankest 1535:
1536: <h4>Response Entity Body</h4>
1537:
1.248 avankest 1538: <p>The <dfn id="response-mime-type">response MIME type</dfn> is the MIME
1539: type the <code>Content-Type</code> header contains without any
1540: parameters or null if the header could not be parsed properly or was
1541: omitted. The <dfn id="override-mime-type">override MIME type</dfn> is
1542: always null. <dfn id="final-mime-type">Final MIME type</dfn> is the
1543: override MIME type unless that is null in which case it is the response
1544: MIME type.</p>
1545:
1546: <p>The <dfn id="response-charset">response charset</dfn> is the value of
1547: the <code>charset</code> parameter of the <code>Content-Type</code> header
1548: or null if there was no <code>charset</code> parameter or if
1549: the header could not be parsed properly or was omitted. The
1550: <dfn id="override-charset">override charset</dfn> is always null.
1551: <dfn id="final-charset">Final charset</dfn> is the override charset unless
1552: that is null in which case it is the response charset.</p>
1.250 avankest 1553:
1.248 avankest 1554:
1555: <p class="note"><span>Override MIME type</span> and
1556: <span>override charset</span> are introduced here solely to make editing
1557: several levels of XMLHttpRequest simultaneously somewhat easier. Apologies
1558: for any confusion they might cause.</p>
1559:
1.250 avankest 1560:
1.248 avankest 1561: <hr>
1562:
1.203 avankest 1563: <p>The <dfn id="response-entity-body">response entity body</dfn> is the
1.255 avankest 1564: fragment of the <span>entity body</span> of the response received so far
1565: (<span title="LOADING state">LOADING</span>) or the complete entity body
1566: of the response (<span title="DONE state">DONE</span>). If the response
1567: does not have an entity body the response entity body is null.</p>
1568:
1569: <p class="note">The <span>response entity body</span> is updated as part
1570: of the <code>send()</code> algorithm.</p>
1.250 avankest 1571:
1.203 avankest 1572: <hr>
1573:
1574: <p>The <dfn id="text-response-entity-body">text response entity body</dfn>
1.248 avankest 1575: is a <code>DOMString</code> representing the <span>response entity
1576: body</span>. The text response entity body is the return value of the
1.203 avankest 1577: following algorithm:</p>
1578:
1579: <ol>
1.248 avankest 1580: <li><p>If the response entity body is null return the empty string and
1581: terminate these steps.</p>
1582:
1583: <li><p>Let <var>charset</var> be the <span>final charset</span>.</p></li>
1.203 avankest 1584:
1.248 avankest 1585: <li><p>Let <var>mime</var> be the <span>final MIME type</span>.</p></li>
1.203 avankest 1586:
1.248 avankest 1587: <li><p>If <var>charset</var> is null and <var>mime</var> is null,
1.203 avankest 1588: <code>text/xml</code>, <code>application/xml</code> or ends in
1.248 avankest 1589: <code title="">+xml</code> use the rules set forth in the XML
1590: specifications to determine the character encoding. Let
1591: <var>charset</var> be the determined character encoding.</p></li>
1592:
1593: <li><p>If <var>charset</var> is null and <var>mime</var> is
1594: <code>text/html</code> follow the rules set forth in the HTML
1595: specification to determine the character encoding. Let
1.203 avankest 1596: <var>charset</var> be the determined character encoding.
1597: [<cite><span>HTML5</span></cite>]</p></li>
1598:
1599: <li>
1600: <p>If <var>charset</var> is null then, for each of the rows in the
1601: following table, starting with the first one and going down, if the first
1602: bytes of <var>bytes</var> match the bytes given in the first column, then
1603: let <var>charset</var> be the encoding given in the cell in the second
1604: column of that row. If there is no match <var>charset</var> remains
1605: null.</p>
1606:
1607: <table>
1608: <thead>
1609: <tr>
1610: <th>Bytes in Hexadecimal
1611: <th>Description
1.237 avankest 1612: <tbody>
1.203 avankest 1613: <tr>
1614: <td>FE FF
1615: <td>UTF-16BE BOM
1616: <tr>
1617: <td>FF FE
1618: <td>UTF-16LE BOM
1619: <tr>
1620: <td>EF BB BF
1.237 avankest 1621: <td>UTF-8 BOM
1.203 avankest 1622: </table>
1623: </li>
1624:
1625: <li><p>If <var>charset</var> is null let <var>charset</var> be
1626: UTF-8.</p></li>
1627:
1628: <li><p>Return the result of decoding the response entity body using
1629: <var>charset</var>. Replace bytes or sequences of bytes that are not
1.248 avankest 1630: valid accordng to the <var>charset</var> with a single
1631: U+FFFD REPLACEMENT CHARACTER character.</p></li>
1.203 avankest 1632: </ol>
1633:
1634: <p class="note">Authors are strongly encouraged to encode their resources
1635: using UTF-8.</p>
1.248 avankest 1636:
1.203 avankest 1637: <hr>
1638:
1.248 avankest 1639: <p>The <dfn id="document-response-entity-body">document response entity
1640: body</dfn> is either a <code>Document</code> representing the
1641: <span>response entity body</span> or null. The document
1642: response entity body is the return value of the following algorithm:</p>
1.12 avankest 1643:
1.203 avankest 1644: <ol>
1645: <li><p>If the <span>response entity body</span> is null terminate these
1.239 avankest 1646: steps and return null.</p></li>
1.12 avankest 1647:
1.248 avankest 1648: <li><p>If <span>final MIME type</span> is not null,
1649: <code>text/xml</code>,
1650: <code>application/xml</code>, and does not end in
1651: <code title="">+xml</code> terminate these steps and return
1652: null.</li>
1653:
1654:
1.203 avankest 1655:
1656: <li>
1.265 avankest 1657: <p>Let <var>document</var> be a
1658: <span>cookie-free <code>Document</code> object</span> that represents
1659: the result of parsing the response entity body into a document tree
1660: following the rules from the XML specifications. If this fails
1661: (unsupported character encoding, namespace well-formedness error et
1662: cetera) terminate these steps return null.
1663: [<cite><span>XML</span></cite>]</p>
1.248 avankest 1664:
1665: <p class="note">Scripts in the resulting document tree will not be executed,
1666: resources referenced will not be loaded and no associated XSLT will be
1667: applied.</p>
1.203 avankest 1668: </li>
1.88 avankest 1669:
1.248 avankest 1670: <li><p>Return <var>document</var>.</p></li>
1.203 avankest 1671: </ol>
1.12 avankest 1672:
1673:
1.248 avankest 1674:
1675:
1676:
1.203 avankest 1677: <h4>The <code title="">responseText</code> attribute</h4>
1.12 avankest 1678:
1.203 avankest 1679: <p>The <dfn id="responsetext"><code>responseText</code></dfn> attribute
1.217 avankest 1680: <em class="ct">must</em> return the result of running these steps:</p>
1.79 avankest 1681:
1.203 avankest 1682: <ol>
1.248 avankest 1683: <li><p>If the state is not <span title="LOADING state">LOADING</span> or
1684: <span title="DONE state">DONE</span> return the empty string and
1.203 avankest 1685: terminate these steps.</p></li>
1.75 avankest 1686:
1.203 avankest 1687: <li><p>Return the <span>text response entity body</span>.</p></li>
1688: </ol>
1.12 avankest 1689:
1690:
1.203 avankest 1691: <h4>The <code title="">responseXML</code> attribute</h4>
1.12 avankest 1692:
1.203 avankest 1693: <p>The <dfn id="responsexml"><code>responseXML</code></dfn> attribute
1.217 avankest 1694: <em class="ct">must</em> return the result of running these steps:</p>
1.12 avankest 1695:
1.203 avankest 1696: <ol>
1697: <li><p>If the state is not <span title="DONE state">DONE</span> return
1.239 avankest 1698: null and terminate these steps.</p></li>
1.12 avankest 1699:
1.248 avankest 1700: <li><p>Return the <span>document response entity body</span>.</p></li>
1.203 avankest 1701: </ol>
1.121 avankest 1702:
1.248 avankest 1703:
1704:
1.12 avankest 1705:
1.240 avankest 1706: <h2 id="exceptions">Exceptions</h2>
1.24 avankest 1707:
1.138 avankest 1708: <p>Several algorithms in this specification may result in an exception
1709: being thrown. These exceptions are all part of the group
1.185 avankest 1710: <code>ExceptionCode</code> and use the <code>DOMException</code> object,
1.138 avankest 1711: which is defined in DOM Level 3 Core. In addition this specification
1712: extends the <code>ExceptionCode</code> group with several new
1713: constants as indicated below. [<cite><span>DOM3Core</span></cite>]</p>
1.203 avankest 1714:
1.193 avankest 1715: <p class="note">Thus, exceptions used by this specification and not
1716: defined in this section are defined by DOM Level 3 Core.</p>
1.31 avankest 1717:
1.138 avankest 1718: <pre class="idl">const unsigned short <span>SECURITY_ERR</span> = 18;
1.199 avankest 1719: const unsigned short <span>NETWORK_ERR</span> = 19;
1720: const unsigned short <span>ABORT_ERR</span> = 20;</pre>
1.31 avankest 1721:
1.138 avankest 1722: <p>The <dfn id="security-err"><code>SECURITY_ERR</code></dfn> exception is
1723: raised if an attempt is made to perform an operation or access some data
1724: in a way that would be a security risk or a violation of the user agent's
1725: security policy.</p>
1726:
1727: <!-- http://lists.w3.org/Archives/Public/public-webapi/2006May/0027.html -->
1728:
1.33 avankest 1729: <p>The <dfn id="network-err"><code>NETWORK_ERR</code></dfn> exception is
1.138 avankest 1730: raised when a network error occurs in synchronous requests.</p>
1.121 avankest 1731:
1.138 avankest 1732: <p>The <dfn id="abort-err"><code>ABORT_ERR</code></dfn> exception is
1733: raised when the user aborts a request in synchronous requests.</p>
1.248 avankest 1734:
1735:
1.203 avankest 1736:
1.240 avankest 1737: <p class="note">These exceptions will be folded into an update of
1.199 avankest 1738: DOM Level 3 Core in due course, as they are appropriate for other API
1739: specifications as well.</p>
1.121 avankest 1740:
1.248 avankest 1741:
1.29 avankest 1742: <h2 class="no-num" id="notcovered">Not in this Specification</h2>
1743:
1.143 avankest 1744: <p><em>This section is non-normative.</em></p>
1.29 avankest 1745:
1.72 avankest 1746: <p>This specification does not include the following features which are
1747: being considered for a future version of this specification:</p>
1.29 avankest 1748:
1749: <ul>
1750: <li><code>load</code> event and <code>onload</code> attribute;</li>
1751: <li><code>error</code> event and <code>onerror</code> attribute;</li>
1752: <li><code>progress</code> event and <code>onprogress</code> attribute;</li>
1753: <li><code title="">abort</code> event and <code>onabort</code> attribute;</li>
1754: <li>Timers have been suggested, perhaps an <code>ontimeout</code>
1755: attribute;</li>
1756: <li>Property to disable following redirects;</li>
1.30 avankest 1757: <li><code title="">responseXML</code> for <code>text/html</code>
1758: documents;</li>
1.203 avankest 1759: <li>Cross-origin <code title="">XMLHttpRequest</code>;</li>
1.87 avankest 1760: <li><code>responseBody</code> to deal with byte streams;</li>
1.114 avankest 1761: <li><code>overrideMimeType</code> to fix up MIME types;</li>
1.87 avankest 1762: <li><code>getRequestHeader()</code> and
1763: <code>removeRequestHeader()</code>.</li>
1.29 avankest 1764: </ul>
1.248 avankest 1765:
1.29 avankest 1766:
1.203 avankest 1767:
1.248 avankest 1768:
1769:
1.203 avankest 1770:
1.248 avankest 1771: <h2 class="no-num" id="references">References</h2>
1.203 avankest 1772:
1.177 avankest 1773: <p>Unless marked "Non-normative" these references are normative.</p>
1.11 avankest 1774:
1.6 avankest 1775: <dl>
1.230 avankest 1776: <dt>[<dfn id="ref-cookies">COOKIES</dfn>]</dt>
1.203 avankest 1777: <dd><cite><a href="http://ietf.org/rfc/rfc2109">HTTP State Management
1.267 ! avankest 1778: Mechanism</a></cite>, D. Kristol, L. Montulli. IETF.</dd>
1.203 avankest 1779: <dd><cite><a href="http://ietf.org/rfc/rfc2965">HTTP State Management
1.267 ! avankest 1780: Mechanism</a></cite>, D. Kristol, L. Montulli. IETF.</dd>
1.211 avankest 1781:
1.203 avankest 1782: <!-- XXX These specs do not match reality. Also, the latter obsoletes the
1783: former -->
1784:
1.248 avankest 1785:
1786:
1.155 avankest 1787: <dt>[<dfn id="ref-dom2events">DOM2Events</dfn>]</dt>
1788: <dd><cite><a href="http://www.w3.org/TR/DOM-Level-2-Events/">Document
1.267 ! avankest 1789: Object Model (DOM) Level 2 Events Specification</a></cite>, T. Pixley.
! 1790: W3C.</dd>
1.155 avankest 1791:
1.145 avankest 1792: <dt>[<dfn id="ref-dom3core">DOM3Core</dfn>]</dt>
1.11 avankest 1793: <dd><cite><a href="http://www.w3.org/TR/DOM-Level-3-Core">Document Object
1.92 avankest 1794: Model (DOM) Level 3 Core Specification</a></cite>, A. Le Hors, P. Le
1.267 ! avankest 1795: Hégaret, L. Wood, G. Nicol, J. Robie, M. Champion, S. Byrne.
! 1796: W3C.</dd>
1.11 avankest 1797:
1.117 avankest 1798: <dt>[<dfn id="ref-ecmascript">ECMAScript</dfn>]</dt>
1.92 avankest 1799: <dd><cite><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">ECMAScript
1.267 ! avankest 1800: Language Specification</a></cite>. ECMA.</dd>
1.248 avankest 1801:
1802:
1.171 avankest 1803:
1.145 avankest 1804: <dt>[<dfn id="ref-html5">HTML5</dfn>]</dt>
1.250 avankest 1805: <dd><cite><a href="http://www.w3.org/html/wg/html5/">HTML5</a></cite>
1.267 ! avankest 1806: (work in progress), I. Hickson. W3C.</dd>
1.250 avankest 1807: <dd><cite><a href="http://www.whatwg.org/specs/html5/current-work/">HTML5</a></cite>
1.267 ! avankest 1808: (work in progress), I. Hickson. WHATWG.</dd>
1.198 avankest 1809:
1810: <dt>[<dfn id="ref-httpverbsec">HTTPVERBSEC</dfn>]</dt>
1.248 avankest 1811: <dd>(Non-normative)
1812: <cite><a href="http://www.kb.cert.org/vuls/id/867593">Multiple vendors'
1813: web servers enable HTTP TRACE method by default</a></cite>, US-CERT.</dd>
1814: <dd>(Non-normative)
1815: <cite><a href="http://www.kb.cert.org/vuls/id/288308">Microsoft Internet
1816: Information Server (IIS) vulnerable to cross-site scripting via HTTP
1817: TRACK method</a></cite>, US-CERT.</dd>
1818: <dd>(Non-normative)
1819: <cite><a href="http://www.kb.cert.org/vuls/id/150227">HTTP proxy default
1820: configurations allow arbitrary TCP connections</a></cite>, US-CERT.</dd>
1821:
1822:
1823:
1824: <dt>[<dfn id="ref-rfc2046">RFC2046</dfn>]</dt>
1825: <dd><cite><a href="http://ietf.org/rfc/rfc2046">Multipurpose Internet Mail
1826: Extensions (MIME) Part Two: Media Types</a></cite>, N. Freed, N.
1.267 ! avankest 1827: Borenstein. IETF.</dd>
1.198 avankest 1828:
1.145 avankest 1829: <dt>[<dfn id="ref-rfc2119">RFC2119</dfn>]</dt>
1.117 avankest 1830: <dd><cite><a href="http://ietf.org/rfc/rfc2119">Key words for use in RFCs to
1.267 ! avankest 1831: Indicate Requirement Levels</a></cite>, S. Bradner. IETF.</dd>
1.12 avankest 1832:
1.248 avankest 1833: <dt>[<dfn id="rfc-rfc2616">RFC2616</dfn>]</dt>
1.11 avankest 1834: <dd><cite><a href="http://ietf.org/rfc/rfc2616">Hypertext Transfer Protocol
1.92 avankest 1835: -- HTTP/1.1</a></cite>, R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L.
1.267 ! avankest 1836: Masinter, P. Leach, T. Berners-Lee. IETF.</dd>
1.12 avankest 1837:
1.37 avankest 1838: <dt>[<dfn id="ref-rfc2617">RFC2617</dfn>]</dt>
1.11 avankest 1839: <dd><cite><a href="http://ietf.org/rfc/rfc2617">HTTP Authentication: Basic
1.92 avankest 1840: and Digest Access Authentication</a></cite>, P. Hallam-Baker, J.
1.267 ! avankest 1841: Hostetler, S. Lawrence, P. Leach, A. Luotonen, L. Stewart. IETF.</dd>
1.12 avankest 1842:
1.37 avankest 1843: <dt>[<dfn id="ref-rfc3986">RFC3986</dfn>]</dt>
1.11 avankest 1844: <dd><cite><a href="http://ietf.org/rfc/rfc3986">Uniform Resource Identifier
1.267 ! avankest 1845: (URI): Generic Syntax</a></cite>, T. Berners-Lee, R. Fielding, L.
! 1846: Masinter. IETF.</dd>
1.184 avankest 1847:
1.248 avankest 1848: <dt>[<dfn id=ref-rfc3987>RFC3987</dfn>]</dt>
1849: <dd><cite><a href="http://ietf.org/rfc/rfc3987">Internationalized
1.267 ! avankest 1850: Resource Identifiers (IRIs)</a></cite>, M. Duerst, M. Suignard.
! 1851: IETF.</dd>
1.248 avankest 1852:
1.203 avankest 1853: <dt>[<dfn id="ref-webidl">WebIDL</dfn>]</dt>
1.200 avankest 1854: <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web
1.267 ! avankest 1855: IDL</a></cite> (work in progress), C. McCormack. W3C.</dd> <!-- XXX add Sam -->
1.181 avankest 1856:
1.92 avankest 1857: <dt>[<dfn id="ref-xml">XML</dfn>]</dt>
1858: <dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup Language
1.267 ! avankest 1859: (XML) 1.0</a></cite>, T. Bray, J. Paoli, C. Sperberg-McQueen, E. Maler,
! 1860: F. Yergeau. W3C.</dd>
! 1861: <dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in
! 1862: XML</a></cite>, T. Bray, D. Hollander, A. Layman, R. Tobin, H. S.
! 1863: Thompson. W3C.</dd>
1.1 avankest 1864: </dl>
1.11 avankest 1865:
1.203 avankest 1866:
1867:
1.130 avankest 1868: <h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
1.11 avankest 1869:
1.159 avankest 1870: <p>The editor would like to thank
1.12 avankest 1871:
1.163 avankest 1872: Addison Phillips,
1.159 avankest 1873: Ahmed Kamel,
1874: Alex Hopmann,
1875: Alex Vincent,
1876: Alexey Proskuryakov,
1877: Asbjørn Ulsberg,
1878: Boris Zbarsky,
1879: Björn Höhrmann,
1880: Cameron McCormack,
1881: Christophe Jolif,
1882: Charles McCathieNevile,
1883: Dan Winship,
1.248 avankest 1884: David Andersson,
1.159 avankest 1885: David Håsäther,
1.248 avankest 1886: David Levin,
1.159 avankest 1887: Dean Jackson,
1888: Denis Sureau,
1889: Doug Schepers,
1890: Douglas Livingstone,
1891: Elliotte Harold,
1892: Eric Lawrence,
1.196 avankest 1893: Erik Dahlström,
1.163 avankest 1894: Geoffrey Sneddon,
1.159 avankest 1895: Gideon Cohn,
1896: Gorm Haug Eriksen,
1.247 avankest 1897: Håkon Wium Lie,
1.159 avankest 1898: Hallvord R. M. Steen,
1.247 avankest 1899: Huub Schaeks,
1.159 avankest 1900: Ian Davis,
1901: Ian Hickson,
1902: Ivan Herman,
1903: Jeff Walden,
1904: Jens Lindström,
1905: Jim Deegan,
1906: Jim Ley,
1907: Joe Farro,
1908: Jonas Sicking,
1909: Julian Reschke,
1910: Karl Dubost,
1.175 avankest 1911: Lachlan Hunt,
1.159 avankest 1912: Maciej Stachowiak,
1913: Magnus Kristiansen,
1914: Marc Hadley,
1915: Marcos Caceres,
1916: Mark Baker,
1.203 avankest 1917: Mark Birbeck,
1.159 avankest 1918: Mark Nottingham,
1.267 ! avankest 1919: Mark S. Miller,
1.248 avankest 1920: Martin Hassman,
1.159 avankest 1921: Mohamed Zergaoui,
1.256 avankest 1922: Olli Pettay,
1.159 avankest 1923: Pawel Glowacki,
1.231 avankest 1924: Peter Michaux,
1.264 avankest 1925: Philip Taylor,
1.159 avankest 1926: Robin Berjon,
1.248 avankest 1927: Rune Halvorsen,
1.159 avankest 1928: Ruud Steltenpool,
1929: Simon Pieters,
1930: Stewart Brodie,
1931: Sunava Dutta,
1.186 avankest 1932: Thomas Roessler,
1.203 avankest 1933: Tom Magliery, and
1.159 avankest 1934: Zhenbin Xu
1.181 avankest 1935:
1.159 avankest 1936: for their contributions to this specification.</p>
1.12 avankest 1937:
1.1 avankest 1938: <p>Special thanks to the Microsoft employees who first implemented the
1.143 avankest 1939: <code title="">XMLHttpRequest</code> interface, which was first widely
1940: deployed by the Windows Internet Explorer browser.</p>
1.12 avankest 1941:
1.143 avankest 1942: <p>Special thanks also to the WHATWG for drafting an initial version of
1943: this specification in their Web Applications 1.0 document (now renamed to
1.250 avankest 1944: HTML5). [<cite><span>HTML5</span></cite>]</p>
1.12 avankest 1945:
1.143 avankest 1946: <p>Thanks also to all those who have helped to improve this specification
1947: by sending suggestions and corrections. (Please, keep bugging us with your
1.22 avankest 1948: issues!)</p>
1.1 avankest 1949: </body>
1950: </html>
1.211 avankest 1951:
Webmaster