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