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