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