Annotation of 2006/webapi/XMLHttpRequest/Overview.src.html, revision 1.116
1.60 avankest 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
1.1 avankest 2: <html lang="en-US">
3: <head>
4: <title>The XMLHttpRequest Object</title>
1.16 avankest 5: <style type="text/css">
6: pre.idl { border:solid thin; background:#eee; color:#000; padding:0.5em }
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.89 avankest 12: .issue { padding:.5em; border:solid #f00 }
1.16 avankest 13: p.issue::before { content:"Issue: " }
14: em.ct { text-transform:lowercase; font-variant:small-caps; font-style:normal }
15: dfn { font-weight:bold; font-style:normal }
16: code { color:orangered }
17: code :link, code :visited { color:inherit }
18: </style>
1.7 avankest 19: <link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base">
1.58 avankest 20: <!--<link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD">-->
1.1 avankest 21: </head>
22: <body>
23: <div class="head">
24: <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 25:
1.10 avankest 26: <h1 class="head">The <code title="">XMLHttpRequest</code> Object</h1>
1.12 avankest 27:
1.53 avankest 28: <h2 class="no-num no-toc" id="pagesubtitle">Editor's draft<!--W3C Working Draft--> [DATE: 3 August 2002]</h2>
1.12 avankest 29:
1.1 avankest 30: <dl>
1.10 avankest 31: <dt>This Version:</dt>
1.24 avankest 32:
1.47 avankest 33: <dd><a href="[VERSION]/">http://www.w3.org/TR/[YEAR]/WD-XMLHttpRequest-[CDATE]/</a></dd>
1.14 avankest 34:
1.10 avankest 35: <dt>Latest Version:</dt>
1.24 avankest 36:
1.1 avankest 37: <dd><a href="http://www.w3.org/TR/XMLHttpRequest/">http://www.w3.org/TR/XMLHttpRequest/</a></dd>
1.14 avankest 38:
1.10 avankest 39: <dt>Previous Versions:</dt>
1.24 avankest 40:
1.58 avankest 41: <dd><a href="http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070227/">http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070227/</a></dd>
42:
1.22 avankest 43: <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060927/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060927/</a></dd>
1.24 avankest 44:
1.1 avankest 45: <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060619/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060619/</a></dd>
1.24 avankest 46:
1.1 avankest 47: <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/</a></dd>
1.14 avankest 48:
1.1 avankest 49: <dt>Editor:</dt>
1.24 avankest 50:
1.1 avankest 51: <dd><a href="http://annevankesteren.nl/">Anne van Kesteren</a>
52: (<a href="http://www.opera.com/">Opera Software ASA</a>)
53: <<a href="mailto:annevk@opera.com">annevk@opera.com</a>></dd>
54: </dl>
1.14 avankest 55:
1.1 avankest 56: <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
1.51 avankest 57: © 2007
58: <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup>
59: (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
60: <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
61: <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C
62: <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
63: <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
64: and
65: <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
66: use</a> rules apply.</p>
1.1 avankest 67: </div>
1.12 avankest 68:
1.1 avankest 69: <hr>
1.12 avankest 70:
1.1 avankest 71: <h2 class="no-num no-toc" id="specabstract">Abstract</h2>
1.10 avankest 72:
1.22 avankest 73: <p>The <code title="">XMLHttpRequest</code> Object specification defines an
74: <abbr title="Application Programming Interface">API</abbr> that provides
75: scripted client functionality for transferring data between a client and a
76: server.</p>
1.12 avankest 77:
1.1 avankest 78: <h2 class="no-num no-toc" id="sotd">Status of this Document</h2>
1.12 avankest 79:
1.1 avankest 80: <p><em>This section describes the status of this document at the time of its
1.36 avankest 81: publication. Other documents may supersede this document. A list of current
82: W3C publications and the latest revision of this technical report can be
83: found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>
84: at http://www.w3.org/TR/.</em></p>
85:
1.63 avankest 86: <!-- change back to Last Call -->
87: <p>This is the [DATE: 3 August 2002] <strong>Editor's</strong> Working
1.54 avankest 88: Draft of The <code title="">XMLHttpRequest</code> Object specification.
1.47 avankest 89: Please send comments to
90: <a href="mailto:public-webapi@w3.org">public-webapi@w3.org</a>
91: (<a href="http://lists.w3.org/Archives/Public/public-webapi/">archived</a>)
92: with either <samp>[XHR]</samp> or <samp title="">[XMLHttpRequest]</samp> at
1.63 avankest 93: the start of the subject line<!-- by 2 April 2007-->.</p>
1.51 avankest 94:
1.47 avankest 95: <p>This document is produced by the
96: <a href="http://www.w3.org/2006/webapi/">Web API Working Group</a>, part of
97: the <a href="http://www.w3.org/2006/rwc/Activity">Rich Web Clients
98: Activity</a> in the W3C <a href="http://www.w3.org/Interaction/">Interaction
1.51 avankest 99: Domain</a>. Changes made to this document can be found in the
1.47 avankest 100: <a href="http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest/Overview.html">W3C
101: public CVS server</a>.</p>
1.12 avankest 102:
1.1 avankest 103: <p>Publication as a Working Draft does not imply endorsement by the W3C
1.36 avankest 104: Membership. This is a draft document and may be updated, replaced or
105: obsoleted by other documents at any time. It is inappropriate to cite this
106: document as other than work in progress.</p>
1.12 avankest 107:
1.1 avankest 108: <p>This document was produced by a group operating under the
1.36 avankest 109: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
1.52 avankest 110: 2004 W3C Patent Policy</a>. W3C maintains a
1.36 avankest 111: <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/38482/status">public
112: list of any patent disclosures</a> made in connection with the deliverables
113: of the group; that page also includes instructions for disclosing a patent.
114: An individual who has actual knowledge of a patent which the individual
115: believes contains
116: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
117: Claim(s)</a> must disclose the information in accordance with
118: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
119: 6 of the W3C Patent Policy</a>.</p>
1.12 avankest 120:
1.1 avankest 121: <h2 class="no-num no-toc" id="toc">Table of Contents</h2>
1.21 avankest 122:
1.1 avankest 123: <!--toc-->
1.12 avankest 124:
1.1 avankest 125: <h2 id="introduction">Introduction</h2>
1.12 avankest 126:
1.1 avankest 127: <p><em>This section is non-normative.</em></p>
1.12 avankest 128:
1.33 avankest 129: <p>The <code>XMLHttpRequest</code> object implements an interface exposed by
130: a scripting engine that allows scripts to perform HTTP client functionality,
1.22 avankest 131: such as submitting form data or loading data from a server.</p>
1.24 avankest 132:
1.1 avankest 133: <p>The name of the object is <code>XMLHttpRequest</code> for compatibility
1.22 avankest 134: with the web, though each component of this name is potentially misleading.
1.39 avankest 135: First, the object supports any text based format, including XML. Second, it
136: can be used to make requests over both HTTP and HTTPS (some implementations
137: support protocols in addition to HTTP and HTTPS, but that functionality is
138: not covered by this specification). Finally, it supports "requests" in a
139: broad sense of the term as it pertains to HTTP; namely all activity involved
140: with HTTP requests or responses for the defined HTTP methods.</p>
1.12 avankest 141:
1.1 avankest 142: <h3 id="examples">Examples of Usage</h3>
1.12 avankest 143:
1.1 avankest 144: <p><em>This section is non-normative.</em></p>
1.12 avankest 145:
1.37 avankest 146: <p>Some [<cite><span>ECMAScript</span></cite>] examples
1.32 avankest 147: are listed in the specification. In addition, you can find some below.</p>
1.14 avankest 148:
149: <div class="example">
150: <p>Some simple code to do something with data from an XML document fetched
1.22 avankest 151: over the network:</p>
1.16 avankest 152:
1.58 avankest 153: <pre><code>function test(data) {
1.14 avankest 154: // taking care of data
155: }
156:
157: function handler() {
158: if(this.readyState == 4 && this.status == 200) {
159: // so far so good
160: if(this.responseXML != null && this.responseXML.getElementById('test').firstChild.data)
161: // success!
162: test(this.responseXML.getElementById('test').firstChild.data);
163: else
164: test(null);
165: } else if (this.readyState == 4 && this.status != 200) {
166: // fetched the wrong page or network error...
167: test(null);
168: }
169: }
1.12 avankest 170:
1.14 avankest 171: var client = new XMLHttpRequest();
172: client.onreadystatechange = handler;
173: client.open("GET", "test.xml");
1.58 avankest 174: client.send();</code></pre>
1.16 avankest 175:
1.56 avankest 176: <p>If you just want to log a message to the server:</p>
1.16 avankest 177:
1.58 avankest 178: <pre><code>function log(message) {
1.14 avankest 179: var client = new XMLHttpRequest();
1.56 avankest 180: client.open("POST", "/log");
1.57 avankest 181: client.setRequestHeader("Content-Type", "text/plain;charset=UTF-8");
1.14 avankest 182: client.send(message);
1.58 avankest 183: }</code></pre>
1.16 avankest 184:
1.14 avankest 185: <p>Or if you want to check the status of a document on the server:</p>
1.16 avankest 186:
1.58 avankest 187: <pre><code>function fetchStatus(address) {
1.14 avankest 188: var client = new XMLHttpRequest();
189: client.onreadystatechange = function() {
190: // in case of network errors this might not give reliable results
191: if(this.readyState == 4)
192: returnStatus(this.status);
193: }
194: client.open("HEAD", address);
195: client.send();
1.58 avankest 196: }</code></pre>
1.14 avankest 197: </div>
1.12 avankest 198:
1.1 avankest 199: <h3 id="conformance">Conformance</h3>
1.12 avankest 200:
1.27 avankest 201: <p>Everything in this specification is normative except for diagrams,
202: examples, notes and sections marked non-normative.</p>
1.12 avankest 203:
1.1 avankest 204: <p>The key words <em class="ct">must</em>, <em class="ct">must not</em>,
1.74 avankest 205: <em class="ct">should</em> and <em class="ct">may</em> in this document are
206: to be interpreted as described in RFC 2119.
207: [<cite><span>RFC2119</span></cite>]</p>
1.12 avankest 208:
1.1 avankest 209: <p>This specification defines the following classes of products:</p>
1.12 avankest 210:
1.1 avankest 211: <dl>
1.74 avankest 212: <dt><dfn id="conforming-user-agent">Conforming user agent</dfn></dt>
1.24 avankest 213:
1.74 avankest 214: <dd>
215: <p>A user agent <em class="ct">must</em> behave as described in this
1.106 avankest 216: specification in order to be considered conformant.</p>
1.95 avankest 217:
1.94 avankest 218: <p>If the user agent does not support XML (including support for
219: namespaces) the <span>XML response entity body</span>
220: <em class="ct">must</em> (always) be <code>null</code>.</p>
1.74 avankest 221:
1.75 avankest 222: <p>User agents <em class="ct">may</em> optimize any algorithm given in
223: this specification, so long as the end result is indistinguishable from
224: the result that would be obtained by the specification's algorithms. (The
225: algorithms in this specification are generally written with more concern
226: for clarity than efficiency.)</p>
1.110 avankest 227:
1.95 avankest 228: <p class="note">This specification uses both the terms "conforming user
229: agent(s)" and "user agent(s)" to refer to this product class.</p>
1.74 avankest 230: </dd>
1.110 avankest 231:
1.94 avankest 232: <dt><dfn id="conforming-xml-user-agent">Conforming XML user agent</dfn></dt>
1.110 avankest 233:
1.94 avankest 234: <dd><p>A user agent that is a <span>conforming user agent</span> and also
235: supports XML (including support for namespaces).</p></dd>
1.1 avankest 236: </dl>
1.32 avankest 237:
1.30 avankest 238: <h4 id="dependencies">Dependencies</h4>
1.33 avankest 239:
1.29 avankest 240: <p>This specification relies on several underlying specifications.</p>
241: <dl>
242: <dt>DOM</dt>
1.33 avankest 243:
1.29 avankest 244: <dd>
1.95 avankest 245: <p><span title="Conforming user agent">Conforming user agents</span>
246: <em class="ct">must</em> support some version of DOM Events and DOM Core,
247: because this specification uses some of the features defined in those
248: specifications. [<cite><span>DOM3Events</span></cite>]
249: [<cite><span>DOM3Core</span></cite>]</p>
250:
251: <p>It <em class="ct">must</em> also support some version of the Window
252: Object because some of the functionality in this specification relies on
253: it. [<cite><span>Window</span></cite>]</p>
1.29 avankest 254: </dd>
255:
256: <dt>HTTP</dt>
1.33 avankest 257:
1.29 avankest 258: <dd>
1.95 avankest 259: <p><span title="Conforming user agent">Conforming user agents</span>
260: <em class="ct">must</em> support some version of the HTTP protocol. The
261: user agent <em class="ct">should</em> support any HTTP method that matches
262: the <span><code>Method</code> production</span> and
263: <em class="ct">must</em> at least support the following methods:</p>
1.58 avankest 264:
265: <ul>
266: <li><code>GET</code></li>
267: <li><code>POST</code></li>
268: <li><code>HEAD</code></li>
269: <li><code>PUT</code></li>
270: <li><code>DELETE</code></li>
271: <li><code>OPTIONS</code></li>
272: </ul>
273:
274: <p>Other requirements regarding HTTP are made throughout the
1.39 avankest 275: specification. [<cite><span>RFC2616</span></cite>]</p>
1.29 avankest 276: </dd>
1.41 avankest 277:
278: <dt>XML</dt>
279:
1.95 avankest 280: <dd><p><span title="Conforming XML user agent">Conforming XML user
281: agents</span> <em class="ct">must</em> support XML (including support for
282: namespaces). [<cite><span>XML</span></cite>]
283: [<cite><span>XMLNS</span></cite>]</p></dd>
1.29 avankest 284: </dl>
1.12 avankest 285:
1.80 avankest 286: <h4 id="terminology">Terminology</h4>
1.12 avankest 287:
1.80 avankest 288: <p>There is a <dfn id="case-insensitive-match">case-insensitive match</dfn>
1.101 avankest 289: of strings <var>s1</var> and <var>s2</var> if after uppercasing both strings
1.100 avankest 290: (by mapping a-z to A-Z) they are identical.</p>
1.80 avankest 291:
292: <h4 id="extensibility">Extensibility</h4>
1.12 avankest 293:
1.81 avankest 294: <p>Extensions of the API defined by this specification are <em>strongly
1.22 avankest 295: discouraged</em>. User agents, Working Groups and other interested parties
1.33 avankest 296: should discuss extensions on a relevant public forum, preferably
1.22 avankest 297: <a href="mailto:public-webapi@w3.org">public-webapi@w3.org</a>.</p>
1.12 avankest 298:
299: <h2 id="xmlhttprequest">The <code title="">XMLHttpRequest</code> Object</h2>
300:
1.58 avankest 301: <p>The <code>XMLHttpRequest</code> object can be used by scripts to
1.22 avankest 302: programmatically connect to their originating server via HTTP.</p>
1.12 avankest 303:
1.1 avankest 304: <p>Objects implementing the <code>XMLHttpRequest</code> interface
1.22 avankest 305: <em class="ct">must</em> also implement the <code>EventTarget</code>
1.58 avankest 306: interface. [<cite><span>DOM3Events</span></cite>]</p>
1.12 avankest 307:
1.58 avankest 308: <p>Objects implementing the <code title="">Window</code> interface
309: <em class="ct">must</em> provide an <code title="">XMLHttpRequest()</code>
310: constructor. [<cite><span>Window</span></cite>]</p>
1.12 avankest 311:
1.1 avankest 312: <div class="example">
1.58 avankest 313: <p>In ECMAScript this can be used as follows:</p>
314: <!-- [<cite><span>ECMAScript</span></cite>] -->
315:
316: <pre><code>var client = new XMLHttpRequest();</code></pre>
1.1 avankest 317: </div>
1.12 avankest 318:
1.58 avankest 319: <p>When the <code title="">XMLHttpRequest()</code> constructor is invoked a
320: persistent pointer to the associated <code title="">Window</code> object
321: <em class="ct">must</em> be stored on the newly created object. This is the
1.25 avankest 322: <dfn title="Window pointer" id="window-pointer"><code>Window</code>
1.58 avankest 323: pointer</dfn>. The associated <code title="">Window</code> object is the one
324: of which the <code title="">XMLHttpRequest</code> constructor was
325: invoked. This <span title="Window pointer">pointer</span>
1.25 avankest 326: <em class="ct">must</em> persist even if the browsing context in which the
1.37 avankest 327: <code title="">Window</code> is located is destroyed (by removing it from a
328: parent browsing context, for instance).</p>
1.25 avankest 329:
1.37 avankest 330: <p>The term browsing context is defined by the <cite>Window Object
331: 1.0</cite> specification. [<cite><span>Window</span></cite>]</p>
1.27 avankest 332:
333: <!-- XXX if the document object changes in the browsing context you get an
1.33 avankest 334: exception in some implementations. -->
1.27 avankest 335:
1.58 avankest 336: <div class="example">
1.65 avankest 337: <p>If <var><code>win</code></var> is a <code title="">Window</code> object
338: <var><code>client</code></var> will have a pointer to
339: <var><code>win</code></var> in the following example:</p>
1.58 avankest 340:
1.65 avankest 341: <pre><code>var client = new win.XMLHttpRequest()</code></pre>
1.58 avankest 342: </div>
1.12 avankest 343:
1.58 avankest 344: <pre class="idl">interface <dfn id="xmlhttprequest-object">XMLHttpRequest</dfn> {
345: // event handler
1.70 avankest 346: attribute EventListener <span>onreadystatechange</span>;
1.58 avankest 347:
348: // state
1.71 avankest 349: const unsigned short <span title="UNSENT state">UNSENT</span> = 0;
1.58 avankest 350: const unsigned short <span title="OPEN state">OPEN</span> = 1;
351: const unsigned short <span title="SENT state">SENT</span> = 2;
1.86 avankest 352: const unsigned short <span title="LOADING state">LOADING</span> = 3;
1.79 avankest 353: const unsigned short <span title="DONE state">DONE</span> = 4;
1.70 avankest 354: readonly attribute unsigned short <span>readyState</span>;
1.58 avankest 355:
356: // request
1.70 avankest 357: void <span>open</span>(in DOMString <var>method</var>, in DOMString <var>url</var>);
358: void <span>open</span>(in DOMString <var>method</var>, in DOMString <var>url</var>, in boolean <var>async</var>);
359: void <span>open</span>(in DOMString <var>method</var>, in DOMString <var>url</var>, in boolean <var>async</var>, in DOMString <var>user</var>);
360: void <span>open</span>(in DOMString <var>method</var>, in DOMString <var>url</var>, in boolean <var>async</var>, in DOMString <var>user</var>, in DOMString <var>password</var>);
361: void <span>setRequestHeader</span>(in DOMString <var>header</var>, in DOMString <var>value</var>);
362: void <span>send</span>();
363: void <span>send</span>(in DOMString <var>data</var>);
364: void <span>send</span>(in Document <var>data</var>);
365: void <span>abort</span>();
1.58 avankest 366:
367: // response
1.70 avankest 368: DOMString <span>getAllResponseHeaders</span>();
369: DOMString <span>getResponseHeader</span>(in DOMString <var>header</var>);
370: readonly attribute DOMString <span>responseText</span>;
371: readonly attribute Document <span>responseXML</span>;
372: readonly attribute unsigned short <span>status</span>;
373: readonly attribute DOMString <span>statusText</span>;
1.1 avankest 374: };</pre>
1.8 avankest 375:
1.58 avankest 376: <p>The <code>XMLHttpRequest</code> object can be in five states:
1.71 avankest 377: <span title="UNSENT state">UNSENT</span>,
1.58 avankest 378: <span title="OPEN state">OPEN</span>, <span title="SENT state">SENT</span>,
1.86 avankest 379: <span title="LOADING state">LOADING</span> and
1.79 avankest 380: <span title="DONE state">DONE</span>. The current state is exposed through
381: the <code>readyState</code> attribute. The method definitions below define
382: when a state transition takes place.</p>
1.58 avankest 383:
384: <p>When constructed, the <code>XMLHttpRequest</code> object
1.71 avankest 385: <em class="ct">must</em> be in the UNSENT state. This state is represented
386: by the <dfn id="unsent" title="UNSENT state"><code>UNSENT</code></dfn>
1.58 avankest 387: constant, whose value is <code>0</code>.</p>
388:
389: <p>The OPEN state is the state of the object when the <code>open()</code>
1.92 avankest 390: method has been successfully invoked. During this state request headers can
1.58 avankest 391: be set using <code>setRequestHeader()</code> and the request can be made
392: using <code>send()</code>. This state is represented by the
393: <dfn id="open" title="OPEN state"><code>OPEN</code></dfn> constant, whose
394: value is <code>1</code>.</p>
395:
1.87 avankest 396: <p>During the OPEN state there is a <dfn id="send-flag"><code>send()</code>
1.104 avankest 397: flag</dfn> which can be either "true" or "false". The initial value of the
398: <code title="">send()</code> flag is "false".</p>
1.87 avankest 399:
1.58 avankest 400: <p>The SENT state is the state of the object when the user agent
401: successfully acknowledged the request. This state is represented by the
402: <dfn id="sent" title="SENT state"><code>SENT</code></dfn> constant, whose
403: value is <code>2</code>.</p>
404:
1.86 avankest 405: <p>The LOADING state is the state of the object when all HTTP headers have
1.58 avankest 406: been received. The object typically remains in this state until the complete
407: message body (if any) has been received. This state is represented by the
1.86 avankest 408: <dfn id="loading" title="LOADING state"><code>LOADING</code></dfn> constant,
409: whose value is <code>3</code>.</p>
1.58 avankest 410:
1.79 avankest 411: <p>The DONE state is the state of the object when either the data transfer
1.58 avankest 412: has been completed or something went wrong during the transfer (infinite
413: redirects for instance). This state is represented by the
1.79 avankest 414: <dfn id="done" title="DONE state"><code>DONE</code></dfn> constant, whose
415: value is <code>4</code>.</p>
1.90 avankest 416:
1.88 avankest 417: <p>The <dfn id="response-entity-body">response entity body</dfn> is the
418: fragment of the <span>entity body</span> received so far (LOADING state) or
419: the complete entity body (DONE state). If there is no entity body the
420: response entity body is "null".</p>
421:
422: <p>The <dfn id="text-response-entity-body">text response entity body</dfn>
1.107 avankest 423: is either a <code>DOMString</code> representing the <span>response entity
424: body</span> or <code>null</code>. The value of the text response entity body
425: <em class="ct">must</em> be determined by running the following
426: algorithm:</p>
1.90 avankest 427:
1.88 avankest 428: <ol>
1.107 avankest 429: <li><p>If the response entity body is "null" return <code>null</code> and
430: terminate these steps.</p>
1.90 avankest 431:
1.113 avankest 432: <li><p>Let <var>charset</var> be "null".</p></li>
1.90 avankest 433:
434: <li><p>If there is no <code>Content-Type</code> header or there is a
435: <code>Content-Type</code> header which contains a MIME type that is
1.116 ! avankest 436: <code>text/xml</code>, <code>application/xml</code> or ends in
! 437: <code title="">+xml</code> (ignoring any parameters) use the rules set forth
! 438: in the XML specification to determine the character encoding. Let
! 439: <var>charset</var> be the determined character encoding.</p></li>
1.90 avankest 440:
1.115 avankest 441: <li>
442: <p>If the <code>Content-Type</code> MIME type contains a
443: <code>charset</code> parameter and <var>charset</var> is "null" let
444: <var>charset</var> be the value of that parameter.</p>
445:
446: <p class="note">The algorithm described by the XML specifications also takes
447: <code>Content-Type</code> into account so whether we override it here or not
448: does not really matter.</p>
449: </li>
1.111 avankest 450:
451: <li>
452: <!-- This stuff is copied from HTML5. Thanks Hixie! -->
1.113 avankest 453: <p>If <var>charset</var> is "null" then, for each of the rows in the
454: following table, starting with the first one and going down, if the start
455: of the entity body (<var>bytes</var>) is equal to or greater than the
456: number of bytes in the first column, and the first bytes of
457: <var>bytes</var> match the bytes given in the first column, then let
458: <var>charset</var> be the encoding given in the cell in the second column
459: of that row. When an encoding is determined or when no encoding is
460: determined go to the next step:</p>
1.111 avankest 461:
462: <table>
463: <thead>
464: <tr>
465: <th>Bytes in Hexadecimal
466: <th>Description
467: <tbody>
468: <tr>
469: <td>00 00 FE FF
470: <td>UTF-32BE BOM
471: <tr>
472: <td>FF FE 00 00
473: <td>UTF-32LE BOM
474: <tr>
475: <td>FE FF
476: <td>UTF-16BE BOM
477: <tr>
478: <td>FF FE
479: <td>UTF-16LE BOM
480: <tr>
481: <td>EF BB BF
482: <td>UTF-8 BOM<!-- nobody uses this
483: <tr>
484: <td>DD 73 66 73
485: <td>UTF-EBCDIC
486: -->
487: </table>
488: </li>
489:
1.113 avankest 490: <li><p>If <var>charset</var> is "null" let <var>charset</var> be
491: UTF-8.</p></li>
492:
1.107 avankest 493: <li><p>Return the result of decoding the response entity body using
494: <var>charset</var>. Or, if that fails, return <code>null</code>.</p></li>
1.88 avankest 495: </ol>
1.90 avankest 496:
1.88 avankest 497: <p>The <dfn id="xml-response-entity-body">XML response entity body</dfn> is
1.107 avankest 498: either a <code>Document</code> representing the <span>response entity
499: body</span> or <code>null</code> and is determined by running the following
500: algorithm (the return value is its value):</p>
1.90 avankest 501:
1.88 avankest 502: <ol>
1.107 avankest 503: <li><p>If the response entity body is "null" terminate these steps and
504: return <code>null</code>.</p></li>
1.88 avankest 505:
1.103 avankest 506: <li><p>If a <code>Content-Type</code> is present and it does not contain a
507: MIME type (ignoring any parameters) that is <code>text/xml</code>,
1.116 ! avankest 508: <code>application/xml</code> or ends in <code title="">+xml</code> terminate
! 509: these steps and return <code>null</code>. (Do not terminate these steps if
! 510: there is no <code>Content-Type</code> header at all.)</p></li>
1.88 avankest 511:
1.107 avankest 512: <li><p>Parse the response entity body following the rules from the XML
513: specifications. Let the result be <var>parsed document</var>. If this fails
514: (unsupported character encoding, namespace well-formedness error et cetera)
515: terminate these steps return <code>null</code>.
1.96 avankest 516: [<cite><span>XML</span></cite>] [<cite><span>XMLNS</span></cite>]</p></li>
1.88 avankest 517:
1.96 avankest 518: <li><p>Return an object implementing the <code>Document</code>
1.88 avankest 519: interface representing the <var>parsed document</var>.</p></li>
520: </ol>
1.58 avankest 521:
1.5 avankest 522: <dl>
1.39 avankest 523: <dt><dfn id="dfn-onreadystatechange"><code>onreadystatechange</code></dfn>
524: of type <code>EventListener</code></dt>
1.12 avankest 525:
1.1 avankest 526: <dd>
527: <p>An attribute that takes an <code>EventListener</code> as value that
1.58 avankest 528: <em class="ct">must</em> be invoked along with any other appropriate event
529: listeners that are registered on this object when a
1.87 avankest 530: <code>readystatechange</code> event is dispatched on it during the
531: bubbling phase. Its initial value <em class="ct">must</em> be
532: <code>null</code>.</p>
1.1 avankest 533: </dd>
1.12 avankest 534:
1.1 avankest 535: <dt><dfn id="dfn-readystate"><code>readyState</code></dfn> of type
1.22 avankest 536: <code>unsigned short</code>, readonly</dt>
1.12 avankest 537:
1.1 avankest 538: <dd>
1.58 avankest 539: <p>The attribute <em class="ct">must</em> be the value of the constant
540: corresponding to the object's current state.</p>
1.1 avankest 541: </dd>
1.12 avankest 542:
1.14 avankest 543: <dt><dfn id="dfn-open" title="open"><code>open(<var>method</var>,
1.22 avankest 544: <var>url</var>, <var>async</var>, <var>user</var>,
545: <var>password</var>)</code></dfn>, method</dt>
1.12 avankest 546:
1.1 avankest 547: <dd>
1.58 avankest 548: <p>When invoked, the user agent <em class="ct">must</em> follow the
1.96 avankest 549: following steps (unless otherwise indicated):</p>
1.58 avankest 550:
551: <ol>
1.97 avankest 552: <li><p>If the <var>method</var> argument does not match the
1.58 avankest 553: <dfn><code>Method</code> production</dfn> defined in section 5.1.1 of RFC
1.98 avankest 554: 2616 raise a <code>SYNTAX_ERR</code> exception and terminate these steps.
1.58 avankest 555: [<cite><span>RFC2616</span></cite>]</p></li>
556:
557: <li><p>If the given <var>method</var> is not supported for security
558: reasons the user agent <em class="ct">should</em> raise a
1.98 avankest 559: <code>SECURITY_ERR</code> exception and terminate these steps.</p></li>
1.58 avankest 560:
561: <li><p>Let <var>stored method</var> be <var>method</var>.</p></li>
562:
1.80 avankest 563: <li><p>If <var>method</var>
564: <span title="case-insensitive match">case-insensitively matches</span>
565: <code>GET</code>, <code>POST</code>, <code>HEAD</code>, <code>PUT</code>,
1.96 avankest 566: <code>DELETE</code> or <code>OPTIONS</code> convert it to its uppercase
567: equivalent (by mapping a-z to A-Z) and let <var>stored method</var> be
568: the result.</p></li>
1.68 avankest 569: <!-- WebKit (and supposedly Firefox) also uppercase: CONNECT, COPY,
570: INDEX, LOCK, M-POST, MKCOL, MOVE, PROPFIND, PROPPATCH, TRACE and UNLOCK.
571: Not sure if TRACE and CONNECT are worth it though. They raise a
572: SECURITY_ERR exception anyway... -->
1.58 avankest 573:
574: <li><p>Drop the fragment identifier (if any) from <var>url</var> and let
575: <var>stored url</var> be the result of that operation.</p></li>
576:
1.96 avankest 577: <li><p>If <var>stored url</var> is a relative reference resolve it using
578: the current value of the <code>baseURI</code> attribute of the
579: <code>Document</code> object currently associated with the
580: <span><code>Window</code> pointer</span>. If this fails raise a
1.98 avankest 581: <code>SYNTAX_ERR</code> exception and terminate these steps.</p></li>
1.58 avankest 582:
1.101 avankest 583: <li><p>If <var>stored url</var> contains an unsupported scheme raise a
584: <code>NOT_SUPPORTED_ERR</code> and terminate these steps.</p></li>
1.110 avankest 585:
1.58 avankest 586: <li><p>If the <code>"user:password"</code> format in the
587: <code>userinfo</code> production defined in section 3.2.1 of RFC 3986 is
588: not supported for the relevant scheme and <var>stored url</var> contains
1.98 avankest 589: this format raise a <code>SYNTAX_ERR</code> and terminate these steps.
1.69 avankest 590: [<cite><span>RFC3986</span></cite>]</p></li>
1.58 avankest 591:
592: <li><p>If <var>stored url</var> contains the <code>"user:password"</code>
593: format let <var>stored user</var> be the user part and <var>stored
594: password</var> be the password part.</p></li>
595:
596: <li><p>If <var>stored url</var> just contains the <code>"user"</code>
597: format let <var>stored user</var> be the user part.</p></li>
598:
1.69 avankest 599: <li>
600: <p>If <var>stored url</var> is non same-origin the user agent
601: <em class="ct">should</em> raise a <code>SECURITY_ERR</code> exception
1.98 avankest 602: and terminate these steps.</p>
1.69 avankest 603: <p class="note">This specification does not define what constitutes as
1.102 avankest 604: non same-origin. It is expected that what constiutes as non same-origin
605: will be defined before this specification eventually reaches the W3C
606: Recommendation status by way of referencing a specification that defines
607: it.<!-- XXX reference HTML5? --></p>
1.69 avankest 608: </li>
1.58 avankest 609:
610: <li><p>Let <var>async</var> be the value of the <var>async</var> argument
1.102 avankest 611: or <code>true</code> if it was omitted.</p></li>
1.58 avankest 612:
613: <li><p>If the <var>user</var> argument was not omitted and its syntax
1.96 avankest 614: does not match that specified by the relevant authentication scheme raise
1.98 avankest 615: a <code>SYNTAX_ERR</code> exception and terminate these steps.</p></li>
1.14 avankest 616:
1.58 avankest 617: <li>
618: <p>If the <var>user</var> argument was not omitted and is not
619: <code>null</code> let <var>stored user</var> be <var>user</var> encoded
620: using the encoding specified in the relevant authentication scheme or
621: UTF-8 if the scheme fails to specify an encoding.</p>
1.14 avankest 622:
1.58 avankest 623: <p class="note">This step overrides any user that may have been set by
624: the <var>url</var> argument.</p>
625: </li>
1.16 avankest 626:
1.58 avankest 627: <li><p>If the <var>user</var> argument was not omitted and is
628: <code>null</code> remove <var>stored user</var>.</p></li>
1.14 avankest 629:
1.58 avankest 630: <li><p>If the <var>password</var> argument was not omitted and its syntax
1.96 avankest 631: does not match that specified by the relevant authentication scheme raise
1.98 avankest 632: a <code>SYNTAX_ERR</code> exception and terminate these steps.</p></li>
1.58 avankest 633:
634: <li><p>If the <var>password</var> argument was not omitted and is not
635: <code>null</code> let <var>stored password</var> be <var>password</var>
636: encoded using the encoding specified in the relevant authentication
637: scheme or UTF-8 if the scheme fails to specify an encoding.</p></li>
638:
639: <li><p>If the <var>password</var> argument was not omitted and is
640: <code>null</code> remove <var>stored password</var>.</p></li>
641:
1.108 avankest 642: <li><p><span title="abort send()">Abort the <code>send()</code>
643: algorithm</span>, set <span>response entity body</span> to "null" and
644: reset the list of request headers.<p></li>
1.58 avankest 645:
1.108 avankest 646: <li><p>The user agent <em class="ct">should</em> cancel any network
647: activity for which the object is responsible.</p></li>
1.58 avankest 648: <!-- we can hardly require it... -->
649:
650: <li><p>Switch the object to the <span title="OPEN state">OPEN</span>
1.105 avankest 651: state, set the <span><code>send()</code> flag</span> to "false" and then
1.104 avankest 652: synchronously dispatch a <code>readystatechange</code> event on the
653: object and return the method call.</p></li>
1.58 avankest 654: </ol>
1.14 avankest 655:
1.19 avankest 656: <p class="note">A future version or extension of this specification will
1.33 avankest 657: most likely define a way of doing cross-site requests.</p>
1.1 avankest 658: </dd>
1.12 avankest 659:
1.14 avankest 660: <dt><dfn id="dfn-setrequestheader" title="setrequestheader"><code>setRequestHeader(<var>header</var>,
1.22 avankest 661: <var>value</var>)</code></dfn>, method</dt>
1.12 avankest 662:
1.5 avankest 663: <dd>
1.45 avankest 664: <p>Each request has a list of request headers with associated values. This
665: method can be used to manipulate those values and set new request
666: headers.</p>
667:
1.58 avankest 668: <p>When invoked, the user agent <em class="ct">must</em> follow the
1.96 avankest 669: following steps (unless otherwise indicated):</p>
1.14 avankest 670:
1.58 avankest 671: <ol>
672: <li><p>If the state of the object is not
1.96 avankest 673: <span title="OPEN state">OPEN</span> raise an
1.98 avankest 674: <code>INVALID_STATE_ERR</code> exception and terminate these
675: steps.</p></li>
1.96 avankest 676:
677: <li><p>If the <span><code>send()</code> flag</span> is "true" raise an
1.98 avankest 678: <code>INVALID_STATE_ERR</code> exception and terminate these
679: steps.</p></li>
1.14 avankest 680:
1.97 avankest 681: <li><p>If the <var>header</var> argument does not match the
1.22 avankest 682: <dfn><code>field-name</code> production</dfn> as defined by section 4.2
1.96 avankest 683: of RFC 2616 or is <code>null</code> raise a <code>SYNTAX_ERR</code>
1.98 avankest 684: exception and terminate these steps.
1.96 avankest 685: [<cite><span>RFC2616</span></cite>]</p></li>
686:
1.98 avankest 687: <li><p>If the <var>value</var> argument is <code>null</code> terminate
688: these steps. (Do not raise an exception.)</li>
1.70 avankest 689: <!-- undefined is to be treated as null here... -->
1.79 avankest 690:
1.97 avankest 691: <li><p>If the <var>value</var> argument does not match the
1.22 avankest 692: <dfn><code>field-value</code> production</dfn> as defined by section 4.2
1.98 avankest 693: of RFC 2616 raise a <code>SYNTAX_ERR</code> and terminate these steps.
1.58 avankest 694: [<cite><span>RFC2616</span></cite>]</p></li>
1.14 avankest 695:
1.32 avankest 696: <li>
1.58 avankest 697: <p>For security reasons these steps <em class="ct">should</em> be
1.98 avankest 698: terminated if the <var>header</var> argument
1.80 avankest 699: <span title="case-insensitive match">case-insensitively matches</span>
700: one of the following headers:</p>
1.58 avankest 701:
1.32 avankest 702: <ul>
703: <li><code>Accept-Charset</code></li>
704: <li><code>Accept-Encoding</code></li>
1.68 avankest 705: <li><code>Connection</code></li>
1.32 avankest 706: <li><code>Content-Length</code></li>
1.68 avankest 707: <li><code>Content-Transfer-Encoding</code></li>
708: <li><code>Date</code></li>
1.32 avankest 709: <li><code>Expect</code></li>
710: <li><code>Host</code></li>
711: <li><code>Keep-Alive</code></li>
712: <li><code>Referer</code></li>
713: <li><code>TE</code></li>
714: <li><code>Trailer</code></li>
715: <li><code>Transfer-Encoding</code></li>
716: <li><code>Upgrade</code></li>
1.68 avankest 717: <li><code>Via</code></li>
1.32 avankest 718: </ul>
719: </li>
1.5 avankest 720:
1.58 avankest 721: <li><p>If the <var>header</var> argument is not in the list of request
1.96 avankest 722: headers append the <var>header</var> with its associated <var>value</var>
1.98 avankest 723: to the list and terminate these steps.</p></li>
1.58 avankest 724:
725: <li><p>If the <var>header</var> argument is in the list of request
1.96 avankest 726: headers either use multiple headers, combine the values or use a
727: combination of those (section 4.2, RFC 2616).
728: [<cite><span>RFC2616</span></cite>]</p></li>
729: <!-- XXX it seems UAs always combine the values -->
1.58 avankest 730: </ol>
1.45 avankest 731:
732: <p class="note">See also the <code>send()</code> method regarding user
1.71 avankest 733: agent header handling for caching, authentication, proxies, and
734: cookies.</p>
1.14 avankest 735:
736: <div class="example">
1.58 avankest 737: <pre><code>// The following script:
1.14 avankest 738: var client = new XMLHttpRequest();
739: client.open('GET', 'demo.cgi');
740: client.setRequestHeader('X-Test', 'one');
741: client.setRequestHeader('X-Test', 'two');
742: client.send();
743:
744: // ...would result in the following header being sent:
745: ...
746: X-Test: one, two
1.58 avankest 747: ...</code></pre>
1.14 avankest 748: </div>
1.5 avankest 749: </dd>
1.12 avankest 750:
1.14 avankest 751: <dt><dfn id="dfn-send" title="send"><code>send(<var>data</var>)</code></dfn>,
1.22 avankest 752: method</dt>
1.12 avankest 753:
1.17 avankest 754: <dd>
1.58 avankest 755: <p>The <code>send()</code> method initiates the request and its optional
1.106 avankest 756: argument provides the <span>entity body</span>. Authors are strongly
757: encouraged to ensure that they have specified the
758: <code>Content-Type</code> header via <code>setRequestHeader()</code>
759: before invoking <code>send()</code> with a non-<code>null</code>
760: <var>data</var> argument.</p>
1.58 avankest 761:
762: <p>When invoked, the user agent <em class="ct">must</em> follow the
1.108 avankest 763: following steps (unless otherwise noted). Note that this algorithm might
1.109 avankest 764: get aborted if the <code>open()</code> or <code>abort()</code> is invoked.
765: When the
766: <dfn title="abort send()" id="abort-send-algorithm"><code>send()</code>
1.110 avankest 767: algorithm is aborted</dfn> the user agent <em class="ct">must</em>
768: terminate the algorithm after finishing the step it is on.</p>
769:
1.108 avankest 770: <p class="note">The following algorithm can not be aborted through script
771: when <var>async</var> is <code>false</code>. It can only be aborted when
772: <var>async</var> is <code>true</code> and only after the method call has
773: returned.</p>
1.58 avankest 774:
775: <ol>
776: <li><p>If the state of the object is not
1.96 avankest 777: <span title="OPEN state">OPEN</span> raise an
1.98 avankest 778: <code>INVALID_STATE_ERR</code> exception and terminate these
779: steps.</p></li>
1.96 avankest 780:
781: <li><p>If the <span><code>send()</code> flag</span> is "true" raise an
1.98 avankest 782: <code>INVALID_STATE_ERR</code> exception and terminate these
783: steps.</p></li>
1.58 avankest 784:
1.102 avankest 785: <li><p>If <var>async</var> is <code>true</code> set the
1.103 avankest 786: <span><code>send()</code> flag</span> to "true".</p></li>
787:
1.58 avankest 788: <li>
789: <p>If the <var>data</var> argument has not been omitted and is not
1.96 avankest 790: <code>null</code> use it for the <dfn id="dfn-entity-body">entity
791: body</dfn> as defined by section 7.2 of RFC 2616 observing the following
792: rules: [<cite><span>RFC2616</span></cite>]</p>
1.58 avankest 793:
794: <dl>
795: <dt><var>data</var> is a <code>DOMString</code></dt>
796:
1.96 avankest 797: <dd><p>Encode <var>data</var> using UTF-8 for transmission.</p></dd>
1.58 avankest 798:
799: <dt><var>data</var> is a <code>Document</code>
800:
801: <dd>
1.96 avankest 802: <p>Serialize <var>data</var> into a namespace well-formed XML document
803: and encoded using the encoding given by
804: <code><var>data</var>.xmlEncoding</code>, if specified, or UTF-8
805: otherwise. Or, if this fails because the <code>Document</code>
806: cannot be serialized act as if <var>data</var> is
807: <code>null</code>.</p>
808:
809: <p>If no <code>Content-Type</code> header is in the list of request
810: headers append it to the list of request headers with a value of
811: <code>application/xml</code>.</p>
1.58 avankest 812:
813: <p class="note">Subsequent changes to the <code>Document</code> have
814: no effect on what is submitted.</p>
815: </dd>
816:
817: <dt><var>data</var> is not a <code>DOMString</code> or
818: <code>Document</code></dt>
819:
1.96 avankest 820: <dd><p>Use the stringification mechanisms of the host language on
821: <var>data</var> and treat the result as if <var>data</var> is a
822: <code>DOMString</code>. Or, if this fails, act as if <var>data</var> is
823: <code>null</code>.</p></dd>
1.58 avankest 824: </dl>
825:
826: <p>If the data argument has been omitted or is <code>null</code> no
1.96 avankest 827: entity body is used in the request.</p>
1.58 avankest 828: </li>
829:
1.71 avankest 830: <li><p>Make a request to <var>stored url</var>, using HTTP method
831: <var>stored method</var>, user <var>stored user</var> (if provided) and
832: password <var>stored password</var> (if provided), taking into account
833: the entity body, list of request headers and the rules listed directly
834: after this set of steps.</p></li>
1.60 avankest 835:
1.67 avankest 836: <li>
1.96 avankest 837: <p>Synchronously dispatch a <code>readystatechange</code> event on the
838: object.</p>
1.67 avankest 839:
1.96 avankest 840: <p class="note">The state of the object does not change. The event is
841: dispatched for historical reasons.</p>
1.67 avankest 842: </li>
843:
1.102 avankest 844: <li><p>If <var>async</var> is <code>true</code> return the
1.98 avankest 845: <code>send()</code> method call. (Do not terminate the steps in the
846: algorithm though.)</p></li>
1.58 avankest 847:
1.82 avankest 848: <li><p>If the request has been successfully acknowledged synchronously
1.104 avankest 849: switch the state to <span title="SENT state">SENT</span>, set the
850: <span><code>send()</code> flag</span> to "false" and then synchronously
851: dispatch a <code>readystatechange</code> event on the object.</p></li>
1.58 avankest 852:
1.101 avankest 853: <li><p>If all HTTP headers have been received, immediately before
1.82 avankest 854: receiving the message body (if any), synchronously switch the state to
1.96 avankest 855: <span title="LOADING state">LOADING</span> and then synchronously
856: dispatch a <code>readystatechange</code> event on the object.</p></li>
1.58 avankest 857:
858: <li>
859: <p>If the response is an HTTP redirect (status code <code>301</code>,
1.96 avankest 860: <code>302</code>, <code>303</code> or <code>307</code>), transparently
861: follow it (unless it violates security, infinite loop precautions or the
862: scheme is not supported).</p>
1.60 avankest 863:
1.58 avankest 864: <p class="note">HTTP places requirements on the user agent regarding the
865: preservation of the request method and entity body during redirects, and
866: also requires users to be notified of certain kinds of automatic
867: redirections.</p>
868: <!-- Arguably HTTP should be fixed for the latter case. No browser
869: follows that as far as I know. -->
870: </li>
1.60 avankest 871:
1.58 avankest 872: <li>
1.96 avankest 873: <p>If something goes wrong (infinite loop, network errors) run the
874: following set of steps:</p>
1.60 avankest 875:
1.58 avankest 876: <ol>
1.96 avankest 877: <li><p>Set <span>response entity body</span> to "null" and reset the
1.89 avankest 878: list of request headers.</p></li>
1.60 avankest 879:
1.82 avankest 880: <li><p>Synchronously switch the state to
1.79 avankest 881: <span title="DONE state">DONE</span>.</p></li>
1.60 avankest 882:
1.96 avankest 883: <li><p>If <var>async</var> is set to <code>false</code> raise a
1.99 avankest 884: <code>NETWORK_ERR</code> exception and terminate the overall
885: algorithm.</p></li>
1.60 avankest 886:
1.58 avankest 887: <li><p>Synchronously dispatch a <code>readystatechange</code> event on
888: the object.</p></li>
1.60 avankest 889:
1.98 avankest 890: <li><p>Terminate the overall algorithm.</p></li>
1.58 avankest 891: </ol>
1.60 avankest 892:
1.82 avankest 893: <p class="note">It is likely that a future version of the
894: <code>XMLHttpRequest</code> object will dispatch an <code>error</code>
895: event here as well.</p>
1.58 avankest 896: </li>
897:
1.82 avankest 898: <li><p>When the request has successfully completed loading, synchronously
1.96 avankest 899: switch the state to <span title="DONE state">DONE</span> and then
900: synchronously dispatch a <code>readystatechange</code> event on the
901: object and return the method call in case of <var>async</var> being
902: <code>false</code>.</p></li>
1.58 avankest 903: </ol>
1.14 avankest 904:
1.91 avankest 905: <p>If the user agent allows the user to configure a proxy it
1.22 avankest 906: <em class="ct">should</em> modify the request appropriately;
1.42 avankest 907: <abbr title="in other words">i.e.</abbr>, connect to the proxy host
908: instead of the origin server, modify the <code>Request-Line</code> and
909: send <code>Proxy-Authorization</code> headers as specified.</p>
1.12 avankest 910:
1.42 avankest 911: <p>If the user agent supports HTTP Authentication it
1.22 avankest 912: <em class="ct">should</em> consider requests originating from this object
1.42 avankest 913: to be part of the protection space that includes the accessed URIs and
914: send <code>Authorization</code> headers and handle <code>401
1.72 avankest 915: Unauthorised</code> requests appropriately. If authentication fails, user
1.42 avankest 916: agents <em class="ct">should</em> prompt the users for credentials.
917: [<cite><span>RFC2617</span></cite>]</p>
918:
1.57 avankest 919: <p>If the user agent supports HTTP State Management it
1.42 avankest 920: <em class="ct">should</em> persist, discard and send cookies (as received
921: in the <code>Set-Cookie</code> and <code>Set-Cookie2</code> response
922: headers, and sent in the <code>Cookie</code> header) as applicable.
923: [<cite><span>RFC2965</span></cite>]</p>
924:
925: <p>If the user agent implements a HTTP cache it <em class="ct">should</em>
926: respect <code>Cache-Control</code> request headers set by the script
927: (<abbr title="for example">e.g.</abbr>, <code>Cache-Control:
928: no-cache</code> bypasses the cache). It <em class="ct">must not</em> send
929: <code>Cache-Control</code> or <code>Pragma</code> request headers
930: automatically unless the user explicitly requests such behaviour
931: (<abbr>e.g.</abbr>, by (force-)reloading the page). <code>304 Not
1.22 avankest 932: Modified</code> responses that are a result of a user agent generated
933: conditional request <em class="ct">must</em> be presented as <code>200
1.57 avankest 934: OK</code> responses with the appropriate content. The user agent
1.39 avankest 935: <em class="ct">must</em> allow scripts to override automatic cache
1.22 avankest 936: validation by setting request headers (e.g., <code>If-None-Match</code>,
1.42 avankest 937: <code>If-Modified-Since</code>), in which case <code>304 Not
938: Modified</code> responses <em class="ct">must</em> be passed through.
939: [<cite><span>RFC2616</span></cite>]</p>
1.12 avankest 940:
1.8 avankest 941: <p>If the user agent implements server-driven content-negotiation
1.42 avankest 942: it <em class="ct">should</em> set <code>Accept-Language</code>,
1.22 avankest 943: <code>Accept-Encoding</code> and <code>Accept-Charset</code> headers as
944: appropriate; it <em class="ct">must not</em> automatically set the
945: <code>Accept</code> header. Responses to such requests
1.40 avankest 946: <em class="ct">must</em> have the content-codings automatically
1.42 avankest 947: decoded. [<cite><span>RFC2616</span></cite>]</p>
1.8 avankest 948: </dd>
1.12 avankest 949:
1.14 avankest 950: <dt><dfn id="dfn-abort"><code>abort()</code></dfn>, method</dt>
1.12 avankest 951:
1.5 avankest 952: <dd>
1.60 avankest 953: <p>When invoked, the user agent <em class="ct">must</em> run the following
1.96 avankest 954: steps (unless otherwise noted):</p>
1.60 avankest 955:
956: <ol>
1.108 avankest 957: <li><p><span title="abort send()">Abort the <code>send()</code>
958: algorithm</span>, set the <span>response entity body</span> to "null",
959: set the <span><code>send()</code> flag</span> to "false" and remove any
1.104 avankest 960: registered request headers.</p></li>
1.60 avankest 961:
1.108 avankest 962: <li><p>The user agent <em class="ct">should</em> cancel any network
963: activity for which the object is responsible.</p></li>
1.60 avankest 964:
1.83 avankest 965: <li>
1.85 avankest 966: <p>If the state is <span title="UNSENT state">UNSENT</span>,
1.83 avankest 967: <span title="OPEN state">OPEN</span> and the <span><code>send()</code>
1.87 avankest 968: flag</span> is "false", or <span title="DONE state">DONE</span> go to
969: the next step.</p>
1.85 avankest 970:
1.96 avankest 971: <p>Otherwise, switch the state to <span title="DONE state">DONE</span>
972: and synchronously dispatch a <code>readystatechange</code> event on the
973: object.</p>
1.83 avankest 974: </li>
1.67 avankest 975:
1.60 avankest 976: <li>
1.97 avankest 977: <p>Switch the state to <span title="UNSENT state">UNSENT</span>. (Do not
1.71 avankest 978: dispatch the <code>readystatechange</code> event.)</p>
1.60 avankest 979:
1.82 avankest 980: <p class="note">It is likely that a future version of the
981: <code>XMLHttpRequest</code> object will dispatch an
982: <code title="">abort</code> event here as well.</p>
1.60 avankest 983: </li>
984: </ol>
1.5 avankest 985: </dd>
1.12 avankest 986:
1.14 avankest 987: <dt><dfn id="dfn-getallresponseheaders"><code>getAllResponseHeaders()</code></dfn>,
1.22 avankest 988: method</dt>
1.12 avankest 989:
1.5 avankest 990: <dd>
1.60 avankest 991: <p>When invoked, the user agent <em class="ct">must</em> run
1.58 avankest 992: the following steps:</p>
993:
994: <ol>
1.86 avankest 995: <li><p>If the state is not <span title="LOADING state">LOADING</span> or
1.96 avankest 996: <span title="DONE state">DONE</span> raise an
1.98 avankest 997: <code>INVALID_STATE_ERR</code> exception and terminate these
998: steps.</p></li>
1.96 avankest 999:
1000: <li><p>Return all the HTTP headers, as a single string, with each header
1001: line separated by a U+000D CR U+000A LF pair excluding the status
1002: line.</p></li>
1.58 avankest 1003: </ol>
1.24 avankest 1004:
1.5 avankest 1005: <div class="example">
1.58 avankest 1006: <pre><code>// The following script:
1.5 avankest 1007: var client = new XMLHttpRequest();
1.14 avankest 1008: client.open("GET", "test.txt", true);
1.5 avankest 1009: client.send();
1.12 avankest 1010: client.onreadystatechange = function() {
1.13 avankest 1011: if(this.readyState == 3) {
1.12 avankest 1012: print(this.getAllResponseHeaders());
1013: }
1014: }
1.5 avankest 1015:
1016: // ...should output something similar to the following text:
1017: Date: 2004年10月24日 04:58:38 GMT
1018: Server: Apache/1.3.31 (Unix)
1019: Keep-Alive: timeout=15, max=99
1020: Connection: Keep-Alive
1021: Transfer-Encoding: chunked
1.58 avankest 1022: Content-Type: text/plain; charset=utf-8</code></pre>
1.5 avankest 1023: </div>
1024: </dd>
1.12 avankest 1025:
1.18 avankest 1026: <dt><dfn id="dfn-getresponseheader" title="getresponseheader"><code>getResponseHeader(<var>header</var>)</code></dfn>,
1.22 avankest 1027: method</dt>
1.12 avankest 1028:
1.1 avankest 1029: <dd>
1.58 avankest 1030: <p>When the method is invoked, the user agent <em class="ct">must</em> run
1031: the following steps:</p>
1.14 avankest 1032:
1.58 avankest 1033: <ol>
1.86 avankest 1034: <li><p>If the state is not <span title="LOADING state">LOADING</span> or
1.96 avankest 1035: <span title="DONE state">DONE</span> raise an
1.98 avankest 1036: <code>INVALID_STATE_ERR</code> exception and terminate these
1037: steps.</p></li>
1.58 avankest 1038:
1.97 avankest 1039: <li><p>If the <var>header</var> argument does not match the
1.96 avankest 1040: <span><code>field-name</code> production</span> raise a
1.98 avankest 1041: <code>SYNTAX_ERR</code> exception and terminate these steps.</p></li>
1.58 avankest 1042:
1.80 avankest 1043: <li><p>If the <var>header</var> argument
1044: <span title="case-insensitive match">case-insensitively matches</span>
1.96 avankest 1045: multiple HTTP headers for the last request sent return the values of
1046: these headers as a single concatenated string separated from each other
1.98 avankest 1047: by an U+002C COMMA followed by an U+0020 SPACE and terminate these
1.96 avankest 1048: steps.</p></li>
1.58 avankest 1049:
1.80 avankest 1050: <li><p>If the <var>header</var> argument
1051: <span title="case-insensitive match">case-insensitively matches</span> a
1.96 avankest 1052: single HTTP header for the last request sent return the value of that
1.98 avankest 1053: header and terminate these steps.</p></li>
1.58 avankest 1054:
1.96 avankest 1055: <li><p>Return <code>null</code>.</p></li>
1.58 avankest 1056: </ol>
1.12 avankest 1057:
1.1 avankest 1058: <div class="example">
1.58 avankest 1059: <pre><code>// The following script:
1.1 avankest 1060: var client = new XMLHttpRequest();
1.14 avankest 1061: client.open("GET", "test.txt", true);
1.5 avankest 1062: client.send();
1.12 avankest 1063: client.onreadystatechange = function() {
1.13 avankest 1064: if(this.readyState == 3) {
1.14 avankest 1065: print(client.getResponseHeader("Content-Type"));
1.12 avankest 1066: }
1067: }
1.1 avankest 1068:
1.5 avankest 1069: // ...should output something similar to the following text:
1.58 avankest 1070: Content-Type: text/plain; charset=utf-8</code></pre>
1.1 avankest 1071: </div>
1.5 avankest 1072: </dd>
1.12 avankest 1073:
1.5 avankest 1074: <dt><dfn id="dfn-responsetext"><code>responseText</code></dfn> of type
1.22 avankest 1075: <code>DOMString</code>, readonly</dt>
1.12 avankest 1076:
1.5 avankest 1077: <dd>
1.88 avankest 1078: <p>On getting, the user agent <em class="ct">must</em> run the following
1079: steps:</p>
1080:
1081: <ol>
1082: <li><p>If the state is not <span title="LOADING state">LOADING</span> or
1.96 avankest 1083: <span title="DONE state">DONE</span> raise an
1.98 avankest 1084: <code>INVALID_STATE_ERR</code> exception and terminate these
1085: steps.</p></li>
1.12 avankest 1086:
1.88 avankest 1087: <li><p>Return the <span>text response entity body</span>.</p></li>
1088: </ol>
1.5 avankest 1089: </dd>
1.12 avankest 1090:
1.5 avankest 1091: <dt><dfn id="dfn-responsexml"><code>responseXML</code></dfn> of type
1.22 avankest 1092: <code>Document</code>, readonly</dt>
1.12 avankest 1093:
1.8 avankest 1094: <dd>
1.75 avankest 1095: <p>On getting, the user agent <em class="ct">must</em> run the following
1096: steps:</p>
1.79 avankest 1097:
1.75 avankest 1098: <ol>
1.96 avankest 1099: <li><p>If the state is not <span title="DONE state">DONE</span> raise an
1.98 avankest 1100: <code>INVALID_STATE_ERR</code> exception and terminate these
1101: steps.</p></li>
1.75 avankest 1102:
1.88 avankest 1103: <li><p>Return the <span>XML response entity body</span>.</p></li>
1.75 avankest 1104: </ol>
1.5 avankest 1105: </dd>
1.12 avankest 1106:
1.22 avankest 1107: <dt><dfn id="dfn-status"><code>status</code></dfn> of type <code>unsigned
1108: short</code>, readonly</dt>
1.12 avankest 1109:
1.5 avankest 1110: <dd>
1.72 avankest 1111: <p>On getting, if available, it <em class="ct">must</em> return the HTTP
1112: status code sent by the server (typically <code>200</code> for a
1113: successful request). Otherwise, if not available, the user agent
1114: <em class="ct">must</em> raise an <code>INVALID_STATE_ERR</code>
1115: exception.</p>
1.12 avankest 1116: </dd>
1117:
1.5 avankest 1118: <dt><dfn id="dfn-statustext"><code>statusText</code></dfn> of type
1.22 avankest 1119: <code>DOMString</code>, readonly</dt>
1.12 avankest 1120:
1.5 avankest 1121: <dd>
1.72 avankest 1122: <p>On getting, if available, it <em class="ct">must</em> return the HTTP
1123: status text sent by the server (appears after the status code). Otherwise,
1124: if not available, the user agent <em class="ct">must</em> raise an
1125: <code>INVALID_STATE_ERR</code> exception.</p>
1.1 avankest 1126: </dd>
1127: </dl>
1.12 avankest 1128:
1.31 avankest 1129: <h3 id="events">Events for the <code title="">XMLHttpRequest</code>
1130: Object</h3>
1.12 avankest 1131:
1.1 avankest 1132: <p>These sections describe the various events that can be dispatched on the
1.22 avankest 1133: object implementing the <code>XMLHttpRequest</code> interface. For this
1134: version of the specification only one event is defined.</p>
1.12 avankest 1135:
1.1 avankest 1136: <dl>
1137: <dt><dfn id="dfn-readystatechange"><code>readystatechange</code></dfn></dt>
1.24 avankest 1138:
1.72 avankest 1139: <dd>When the user agent dispatches a <code title="">readystatechange</code>
1140: event (as indicated above) it <em class="ct">must not</em> bubble,
1141: <em class="ct">must not</em> be cancelable and <em class="ct">must</em>
1142: implement the <code>Event</code> interface. Its <code>namespaceURI</code>
1143: attribute <em class="ct">must</em> be <code>null</code>.
1144: [<cite><span>DOM3Events</span></cite>]</dd>
1.1 avankest 1145: </dl>
1.32 avankest 1146:
1.31 avankest 1147: <h3 id="exceptions">Exceptions for the <code title="">XMLHttpRequest</code>
1148: Object</h3>
1149:
1.32 avankest 1150: <pre class="idl">exception <dfn>XMLHttpRequestException</dfn> {
1.31 avankest 1151: unsigned short code;
1152: };
1153: const unsigned short <span>NETWORK_ERR</span> = 101;</pre>
1154:
1.33 avankest 1155: <p>The <dfn id="network-err"><code>NETWORK_ERR</code></dfn> exception is
1156: thrown when a network error occurs in synchronous requests. See the section
1157: on <code>send()</code> for more details.</p>
1.11 avankest 1158:
1.29 avankest 1159: <h2 class="no-num" id="notcovered">Not in this Specification</h2>
1160:
1161: <p><em>This section is non normative.</em></p>
1162:
1.72 avankest 1163: <p>This specification does not include the following features which are
1164: being considered for a future version of this specification:</p>
1.29 avankest 1165:
1166: <ul>
1167: <li><code>load</code> event and <code>onload</code> attribute;</li>
1168: <li><code>error</code> event and <code>onerror</code> attribute;</li>
1169: <li><code>progress</code> event and <code>onprogress</code> attribute;</li>
1170: <li><code title="">abort</code> event and <code>onabort</code> attribute;</li>
1171: <li>Timers have been suggested, perhaps an <code>ontimeout</code>
1172: attribute;</li>
1173: <li>Property to disable following redirects;</li>
1.30 avankest 1174: <li><code title="">responseXML</code> for <code>text/html</code>
1175: documents;</li>
1.40 avankest 1176: <li>Cross-site <code title="">XMLHttpRequest</code>;</li>
1.87 avankest 1177: <li><code>responseBody</code> to deal with byte streams;</li>
1.114 avankest 1178: <li><code>overrideMimeType</code> to fix up MIME types;</li>
1.87 avankest 1179: <li><code>getRequestHeader()</code> and
1180: <code>removeRequestHeader()</code>.</li>
1.29 avankest 1181: </ul>
1182:
1.1 avankest 1183: <h2 class="no-num" id="bibref">References</h2>
1.11 avankest 1184:
1.6 avankest 1185: <dl>
1.37 avankest 1186: <dt>[<dfn id="DOM3">DOM3Core</dfn>]</dt>
1.24 avankest 1187:
1.11 avankest 1188: <dd><cite><a href="http://www.w3.org/TR/DOM-Level-3-Core">Document Object
1.92 avankest 1189: Model (DOM) Level 3 Core Specification</a></cite>, A. Le Hors, P. Le
1190: Hégaret, L. Wood, G. Nicol, J. Robie, M. Champion, S. Byrne, editors. World
1191: Wide Web Consortium, April 2004.</dd>
1.11 avankest 1192:
1.37 avankest 1193: <dt>[<dfn id="DOM3EV">DOM3Events</dfn>]</dt>
1.24 avankest 1194:
1.92 avankest 1195: <dd><cite><a href="http://www.w3.org/TR/DOM-Level-3-Events/">Document
1196: Object Model (DOM) Level 3 Events Specification</a></cite>, Björn Höhrmann,
1197: editor. World Wide Web Consortium, April 2006.</dd>
1.11 avankest 1198:
1.37 avankest 1199: <dt>[<dfn id="ref-ecmascript">ECMAScript</dfn>]</dt>
1.24 avankest 1200:
1.92 avankest 1201: <dd><cite><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">ECMAScript
1202: Language Specification</a></cite>, Third Edition. ECMA, December 1999.</dd>
1.14 avankest 1203:
1.37 avankest 1204: <dt>[<dfn id="ref-rfc2046">RFC2046</dfn>]</dt>
1.24 avankest 1205:
1.19 avankest 1206: <dd><cite><a href="http://ietf.org/rfc/rfc2046">Multipurpose Internet Mail
1.92 avankest 1207: Extensions (MIME) Part Two: Media Types</a></cite>, N. Freed, N.
1208: Borenstein, editors. IETF, November 1996.</dd>
1.14 avankest 1209:
1.37 avankest 1210: <dt>[<dfn id="RFC2119">RFC2119</dfn>]</dt>
1.24 avankest 1211:
1.92 avankest 1212: <dd><cite><a href="http://ietf.org/rfc/rfc2119">RFC 2119: Key words for use
1213: in RFCs to Indicate Requirement Levels</a></cite>, S. Bradner. IETF, March
1214: 1997.</dd>
1.12 avankest 1215:
1.37 avankest 1216: <dt>[<dfn id="RFC2616">RFC2616</dfn>]</dt>
1.24 avankest 1217:
1.11 avankest 1218: <dd><cite><a href="http://ietf.org/rfc/rfc2616">Hypertext Transfer Protocol
1.92 avankest 1219: -- HTTP/1.1</a></cite>, R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L.
1220: Masinter, P. Leach, T. Berners-Lee, editors. IETF, June 1999.</dd>
1.12 avankest 1221:
1.37 avankest 1222: <dt>[<dfn id="ref-rfc2617">RFC2617</dfn>]</dt>
1.24 avankest 1223:
1.11 avankest 1224: <dd><cite><a href="http://ietf.org/rfc/rfc2617">HTTP Authentication: Basic
1.92 avankest 1225: and Digest Access Authentication</a></cite>, P. Hallam-Baker, J.
1226: Hostetler, S. Lawrence, P. Leach, A. Luotonen, L. Stewart, editors. IETF,
1227: June 1999.</dd>
1.12 avankest 1228:
1.37 avankest 1229: <dt>[<dfn id="ref-rfc2965">RFC2965</dfn>]</dt>
1.24 avankest 1230:
1.19 avankest 1231: <dd><cite><a href="http://ietf.org/rfc/rfc2965">HTTP State Management
1.92 avankest 1232: Mechanism</a></cite>, D. Kristol, L. Montulli, editors. IETF, October
1233: 2000.</dd>
1.19 avankest 1234:
1.37 avankest 1235: <dt>[<dfn id="ref-rfc3986">RFC3986</dfn>]</dt>
1.24 avankest 1236:
1.11 avankest 1237: <dd><cite><a href="http://ietf.org/rfc/rfc3986">Uniform Resource Identifier
1.92 avankest 1238: (URI): Generic Syntax</a></cite>, T. Berners-Lee, R. Fielding, L. Masinter,
1239: editors. IETF, January 2005.</dd>
1.28 avankest 1240:
1.92 avankest 1241: <dt>[<dfn id="ref-window">Window</dfn>]</dt>
1.28 avankest 1242:
1.92 avankest 1243: <dd><cite><a href="http://www.w3.org/TR/Window/">Window Object
1244: 1.0</a></cite>, I. Davis, M. Stachowiak, editors. W3C, April 2006.</dd>
1.41 avankest 1245:
1.92 avankest 1246: <dt>[<dfn id="ref-xml">XML</dfn>]</dt>
1.41 avankest 1247:
1.92 avankest 1248: <dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup Language
1249: (XML) 1.0 (Fourth Edition)</a></cite>, T. Bray, J. Paoli, C.
1250: Sperberg-McQueen, E. Maler, F. Yergeau. W3C, September 2006.</dd>
1.41 avankest 1251:
1.92 avankest 1252: <dt>[<dfn id="ref-xmlns">XMLNS</dfn>]</dt>
1.41 avankest 1253:
1.92 avankest 1254: <dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in XML
1255: (Second Edition)</a></cite>, T. Bray, D. Hollander, A. Layman, R. Tobin.
1256: W3C, August 2006.</dd>
1.1 avankest 1257: </dl>
1.11 avankest 1258:
1.1 avankest 1259: <h2 class="no-num" id="acknowledgements">Acknowledgements</h2>
1.11 avankest 1260:
1.1 avankest 1261: <p><em>This section is non-normative</em></p>
1.12 avankest 1262:
1.7 avankest 1263: <p>The editor would like to thank to the following people who have contributed
1.33 avankest 1264: to this specification (ordered by first name):</p>
1.12 avankest 1265:
1.1 avankest 1266: <ul>
1.112 avankest 1267: <li>Ahmed Kamel</li>
1.22 avankest 1268: <li>Alex Hopmann</li>
1.7 avankest 1269: <li>Alex Vincent</li>
1.15 avankest 1270: <li>Alexey Proskuryakov</li>
1.1 avankest 1271: <li>Asbjørn Ulsberg</li>
1272: <li>Boris Zbarsky</li>
1273: <li>Björn Höhrmann</li>
1274: <li>Cameron McCormack</li>
1275: <li>Christophe Jolif</li>
1276: <li>Charles McCathieNevile</li>
1.54 avankest 1277: <li>Dan Winship</li>
1.72 avankest 1278: <li>David Håsäther</li>
1.1 avankest 1279: <li>Dean Jackson</li>
1280: <li>Doug Schepers</li>
1281: <li>Douglas Livingstone</li>
1.112 avankest 1282: <li>Eric Lawrence</li>
1283: <li>Gideon Cohn</li>
1.1 avankest 1284: <li>Gorm Haug Eriksen</li>
1285: <li>Hallvord R. M. Steen</li>
1286: <li>Håkon Wium Lie</li>
1287: <li>Ian Davis</li>
1288: <li>Ian Hickson</li>
1289: <li>Ivan Herman</li>
1290: <li>Jens Lindström</li>
1291: <li>Jim Deegan</li>
1292: <li>Jim Ley</li>
1.112 avankest 1293: <li>Joe Farro</li>
1.1 avankest 1294: <li>Jonas Sicking</li>
1295: <li>Julian Reschke</li>
1296: <li>Karl Dubost</li>
1297: <li>Maciej Stachowiak</li>
1.7 avankest 1298: <li>Magnus Kristiansen</li>
1.1 avankest 1299: <li>Marc Hadley</li>
1.53 avankest 1300: <li>Marcos Caceres</li>
1.87 avankest 1301: <li>Mark Baker</li>
1.1 avankest 1302: <li>Mark Nottingham</li>
1.92 avankest 1303: <li>Mohamed Zergaoui</li>
1.1 avankest 1304: <li>Pawel Glowacki</li>
1305: <li>Robin Berjon</li>
1306: <li>Ruud Steltenpool</li>
1.33 avankest 1307: <li>Simon Pieters</li>
1.112 avankest 1308: <li>Sunava Dutta</li>
1309: <li>Zhenbin Xu</li>
1.1 avankest 1310: </ul>
1.12 avankest 1311:
1.1 avankest 1312: <p>Special thanks to the Microsoft employees who first implemented the
1.22 avankest 1313: <code>XMLHttpRequest</code> interface, which was first widely deployed by the
1314: Windows Internet Explorer browser.</p>
1.12 avankest 1315:
1.54 avankest 1316: <p>Special thanks also to the WHATWG for drafting an initial version of this
1.22 avankest 1317: specification in their Web Applications 1.0 document.</p>
1.12 avankest 1318:
1.1 avankest 1319: <p>Thanks also to all those who have helped to improve this specification by
1.22 avankest 1320: sending suggestions and corrections. (Please, keep bugging us with your
1321: issues!)</p>
1.1 avankest 1322: </body>
1323: </html>
Webmaster