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