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