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