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