Annotation of 2006/webapi/XMLHttpRequest/Overview.src.html, revision 1.279
1.248 avankest 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
1.1 avankest 2: <html lang="en-US">
3: <head>
1.207 avankest 4: <title>XMLHttpRequest</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.203 avankest 12: .XXX { padding:.5em; border:solid #f00 }
13: p.XXX::before { content:"Issue: " }
1.119 avankest 14: dl.switch { padding-left:2em }
1.248 avankest 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.269 avankest 17: dl.domintro { color: green; margin: 2em 0 2em 2em; padding: 0.5em 1em; border: none; background: #DDFFDD; }
18: dl.domintro dt, dl.domintro dt * { color: black; text-decoration: none; }
19: dl.domintro dd { margin: 0.5em 0 1em 2em; padding: 0; }
20: dl.domintro dd p { margin: 0.5em 0; }
21: dl.domintro:before { display: table; margin: -1em -0.5em -0.5em auto; width: auto; content: 'This box is non-normative. Implementation requirements are given below this box.'; color: red; border: solid 2px; background: white; padding: 0 0.25em; }
1.16 avankest 22: em.ct { text-transform:lowercase; font-variant:small-caps; font-style:normal }
23: dfn { font-weight:bold; font-style:normal }
24: code { color:orangered }
25: code :link, code :visited { color:inherit }
1.203 avankest 26: hr:not(.top) { display:block; background:none; border:none; padding:0; margin:2em 0; height:auto }
27: table { border-collapse:collapse; border-style:hidden hidden none hidden }
28: table thead { border-bottom:solid }
29: table tbody th:first-child { border-left:solid }
30: table td, table th { border-left:solid; border-right:solid; border-bottom:solid thin; vertical-align:top; padding:0.2em }
1.16 avankest 31: </style>
1.147 avankest 32: <link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-[STATUS]">
1.1 avankest 33: </head>
34: <body>
35: <div class="head">
36: <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 37:
1.229 avankest 38: <h1 class="head" id="the-xmlhttprequest-object">XMLHttpRequest</h1>
1.248 avankest 39:
1.12 avankest 40:
1.149 avankest 41: <h2 class="no-num no-toc" id="w3c-doctype">[LONGSTATUS] [DATE: 3 August 2002]</h2>
1.12 avankest 42:
1.1 avankest 43: <dl>
1.10 avankest 44: <dt>This Version:</dt>
1.246 avankest 45: <dd><a href="[VERSION]/">http://www.w3.org/TR/[YEAR]/ED-XMLHttpRequest-[CDATE]/</a></dd>
1.14 avankest 46:
1.10 avankest 47: <dt>Latest Version:</dt>
1.1 avankest 48: <dd><a href="http://www.w3.org/TR/XMLHttpRequest/">http://www.w3.org/TR/XMLHttpRequest/</a></dd>
1.203 avankest 49:
1.189 avankest 50: <dt>Latest Editor Version:</dt>
51: <dd><a href="http://dev.w3.org/2006/webapi/XMLHttpRequest/">http://dev.w3.org/2006/webapi/XMLHttpRequest/</a></dd>
1.14 avankest 52:
1.10 avankest 53: <dt>Previous Versions:</dt>
1.248 avankest 54:
1.231 avankest 55: <dd><a href="http://www.w3.org/TR/2009/WD-XMLHttpRequest-20090820/">http://www.w3.org/TR/2009/WD-XMLHttpRequest-20090820/</a></dd>
1.173 avankest 56: <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 57: <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 58: <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 59: <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 60: <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 61: <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060619/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060619/</a></dd>
62: <dd><a href="http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/">http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/</a></dd>
1.248 avankest 63:
64:
1.14 avankest 65:
1.1 avankest 66: <dt>Editor:</dt>
67: <dd><a href="http://annevankesteren.nl/">Anne van Kesteren</a>
68: (<a href="http://www.opera.com/">Opera Software ASA</a>)
69: <<a href="mailto:annevk@opera.com">annevk@opera.com</a>></dd>
70: </dl>
1.14 avankest 71:
1.1 avankest 72: <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
1.229 avankest 73: © 2009
1.51 avankest 74: <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup>
75: (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
76: <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
77: <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C
78: <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
79: <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
80: and
81: <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
82: use</a> rules apply.</p>
1.1 avankest 83: </div>
1.12 avankest 84:
1.1 avankest 85: <hr>
1.12 avankest 86:
1.1 avankest 87: <h2 class="no-num no-toc" id="specabstract">Abstract</h2>
1.10 avankest 88:
1.248 avankest 89:
90:
1.229 avankest 91: <p>The XMLHttpRequest specification defines an API
1.207 avankest 92: that provides scripted client functionality for transferring data between
93: a client and a server.</p>
1.248 avankest 94:
1.12 avankest 95:
1.1 avankest 96: <h2 class="no-num no-toc" id="sotd">Status of this Document</h2>
1.12 avankest 97:
1.1 avankest 98: <p><em>This section describes the status of this document at the time of its
1.36 avankest 99: publication. Other documents may supersede this document. A list of current
100: W3C publications and the latest revision of this technical report can be
101: found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>
1.117 avankest 102: at http://www.w3.org/TR/.</em></p>
1.36 avankest 103:
1.248 avankest 104: <p>This is the [DATE: 3 August 2002] <!--Last Call Working Draft-->[LONGSTATUS] of
105: XMLHttpRequest. Please send comments to
106: <a href="mailto:public-webapps@w3.org?subject=[XHR]%20">public-webapps@w3.org</a>
1.207 avankest 107: (<a href="http://lists.w3.org/Archives/Public/public-webapps/">archived</a>)
1.248 avankest 108: with <samp>[XHR]</samp> at the start of the subject line.</p>
1.51 avankest 109:
1.47 avankest 110: <p>This document is produced by the
1.248 avankest 111: <a href="http://www.w3.org/2008/webapps/">Web Applications</a> (WebApps) Working Group.
112: The WebApps Working Group is part of the
1.207 avankest 113: <a href="http://www.w3.org/2006/rwc/Activity">Rich Web Clients Activity</a>
1.248 avankest 114: in the W3C <a href="http://www.w3.org/Interaction/">Interaction Domain</a>.</p>
1.12 avankest 115:
1.1 avankest 116: <p>This document was produced by a group operating under the
1.248 avankest 117: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004
118: W3C Patent Policy</a>. W3C maintains a
1.207 avankest 119: <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/42538/status">public
1.248 avankest 120: list of any patent disclosures</a> made in connection with the deliverables of
121: the group; that page also includes instructions for disclosing a patent. An
122: individual who has actual knowledge of a patent which the individual believes
123: contains
1.36 avankest 124: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
125: Claim(s)</a> must disclose the information in accordance with
126: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
127: 6 of the W3C Patent Policy</a>.</p>
1.12 avankest 128:
1.248 avankest 129: <p>Publication as a Working Draft does not imply endorsement by the W3C
130: Membership. This is a draft document and may be updated, replaced or
131: obsoleted by other documents at any time. It is inappropriate to cite this
132: document as other than work in progress.</p>
1.268 avankest 133:
134:
135: <h3 class="no-num no-toc" id="crec">Candidate Recommendation Exit Criteria</h3>
136:
137: <p>To exit the Candidate Recommendation (CR) stage the following criteria
138: <em class="ct">must</em> have been met:</p>
139:
140: <ol>
141: <li>There will be at least two interoperable implementations passing all
142: test cases in the test suite for this specification. An implementation is
143: to be available (i.e. for download), shipping (i.e. not private), and not
144: experimental (i.e. intended for a wide audience). The working group will
145: decide when the test suite is of sufficient quality to test
146: interoperability.</li>
147:
148: <li>A minimum of six months of the CR stage will have elapsed. This is to
149: ensure that enough time is given for any remaining major errors to be
150: caught. The CR period will be extended if implementations are slow to
151: appear.</li>
152: </ol>
153:
154: <p>An update to this draft will point to the test suite.</p>
155:
1.207 avankest 156:
157:
1.1 avankest 158: <h2 class="no-num no-toc" id="toc">Table of Contents</h2>
1.21 avankest 159:
1.1 avankest 160: <!--toc-->
1.12 avankest 161:
1.207 avankest 162:
163:
1.1 avankest 164: <h2 id="introduction">Introduction</h2>
1.12 avankest 165:
1.1 avankest 166: <p><em>This section is non-normative.</em></p>
1.12 avankest 167:
1.183 avankest 168: <p>The <code>XMLHttpRequest</code> object implements an interface exposed
169: by a scripting engine that allows scripts to perform HTTP client
170: functionality, such as submitting form data or loading data from a
171: server. It is the ECMAScript HTTP API.</p>
1.24 avankest 172:
1.1 avankest 173: <p>The name of the object is <code>XMLHttpRequest</code> for compatibility
1.183 avankest 174: with the Web, though each component of this name is potentially
175: misleading. First, the object supports any text based format, including
176: XML. Second, it can be used to make requests over both HTTP and HTTPS
177: (some implementations support protocols in addition to HTTP and HTTPS, but
178: that functionality is not covered by this specification). Finally, it
179: supports "requests" in a broad sense of the term as it pertains to HTTP;
180: namely all activity involved with HTTP requests or responses for the
181: defined HTTP methods.</p>
1.12 avankest 182:
1.14 avankest 183: <div class="example">
1.250 avankest 184: <p>Some simple code to do something with data from an XML document
185: fetched over the network:</p>
1.16 avankest 186:
1.58 avankest 187: <pre><code>function test(data) {
1.14 avankest 188: // taking care of data
189: }
190:
191: function handler() {
1.117 avankest 192: if(this.readyState == 4 && this.status == 200) {
1.14 avankest 193: // so far so good
1.117 avankest 194: if(this.responseXML != null && this.responseXML.getElementById('test').firstChild.data)
195: // success!
1.14 avankest 196: test(this.responseXML.getElementById('test').firstChild.data);
197: else
198: test(null);
1.117 avankest 199: } else if (this.readyState == 4 && this.status != 200) {
1.14 avankest 200: // fetched the wrong page or network error...
201: test(null);
202: }
203: }
1.12 avankest 204:
1.14 avankest 205: var client = new XMLHttpRequest();
206: client.onreadystatechange = handler;
1.250 avankest 207: client.open("GET", "unicorn.xml");
1.58 avankest 208: client.send();</code></pre>
1.16 avankest 209:
1.56 avankest 210: <p>If you just want to log a message to the server:</p>
1.16 avankest 211:
1.58 avankest 212: <pre><code>function log(message) {
1.14 avankest 213: var client = new XMLHttpRequest();
1.56 avankest 214: client.open("POST", "/log");
1.57 avankest 215: client.setRequestHeader("Content-Type", "text/plain;charset=UTF-8");
1.14 avankest 216: client.send(message);
1.58 avankest 217: }</code></pre>
1.16 avankest 218:
1.14 avankest 219: <p>Or if you want to check the status of a document on the server:</p>
1.16 avankest 220:
1.58 avankest 221: <pre><code>function fetchStatus(address) {
1.14 avankest 222: var client = new XMLHttpRequest();
223: client.onreadystatechange = function() {
224: // in case of network errors this might not give reliable results
225: if(this.readyState == 4)
226: returnStatus(this.status);
227: }
228: client.open("HEAD", address);
229: client.send();
1.58 avankest 230: }</code></pre>
1.14 avankest 231: </div>
1.12 avankest 232:
1.203 avankest 233:
234:
1.248 avankest 235:
236: <h2 id="conformance">Conformance Criteria</h2>
1.12 avankest 237:
1.27 avankest 238: <p>Everything in this specification is normative except for diagrams,
239: examples, notes and sections marked non-normative.</p>
1.12 avankest 240:
1.1 avankest 241: <p>The key words <em class="ct">must</em>, <em class="ct">must not</em>,
1.259 avankest 242: <em class="ct">should</em>, <em class="ct">should not</em>, and
243: <em class="ct">may</em> in this document are to be interpreted as
244: described in RFC 2119. [<cite><span>RFC2119</span></cite>]</p>
1.12 avankest 245:
1.1 avankest 246: <p>This specification defines the following classes of products:</p>
1.12 avankest 247:
1.1 avankest 248: <dl>
1.74 avankest 249: <dt><dfn id="conforming-user-agent">Conforming user agent</dfn></dt>
1.24 avankest 250:
1.74 avankest 251: <dd>
252: <p>A user agent <em class="ct">must</em> behave as described in this
1.106 avankest 253: specification in order to be considered conformant.</p>
1.95 avankest 254:
1.248 avankest 255:
1.224 avankest 256: <p>If the user agent is not a <span>conforming XML user agent</span> the
257: <span>XML response entity body</span> <em class="ct">must</em> (always)
1.239 avankest 258: be null.</p>
1.248 avankest 259:
1.140 avankest 260:
261: <p>User agents <em class="ct">may</em> implement algorithms given in
262: this specification in any way desired, so long as the end result is
263: indistinguishable from the result that would be obtained by the
264: specification's algorithms.</p>
1.110 avankest 265:
1.95 avankest 266: <p class="note">This specification uses both the terms "conforming user
267: agent(s)" and "user agent(s)" to refer to this product class.</p>
1.74 avankest 268: </dd>
1.248 avankest 269:
1.94 avankest 270: <dt><dfn id="conforming-xml-user-agent">Conforming XML user agent</dfn></dt>
1.110 avankest 271:
1.224 avankest 272: <dd><p>An XML user agent <em class="ct">must</em> be a
273: <span>conforming user agent</span> and <em class="ct">must</em> be a
274: conforming XML processor that reports violations of
275: namespace well-formedness. [<cite><span>XML</span></cite>]</p></dd>
1.248 avankest 276:
1.1 avankest 277: </dl>
1.32 avankest 278:
1.153 avankest 279: <h3 id="dependencies">Dependencies</h3>
1.33 avankest 280:
1.29 avankest 281: <p>This specification relies on several underlying specifications.</p>
1.248 avankest 282:
1.29 avankest 283: <dl>
1.248 avankest 284:
285:
1.29 avankest 286: <dt>DOM</dt>
1.33 avankest 287:
1.155 avankest 288: <dd><p>A <span title="conforming user agent">conforming user agent</span>
1.176 avankest 289: <em class="ct">must</em> support at least the subset of the functionality
1.182 avankest 290: defined in DOM Events and DOM Core that this specification relies upon,
291: such as various exceptions and <code>EventTarget</code>.
1.155 avankest 292: [<cite><span>DOM2Events</span></cite>]
293: [<cite><span>DOM3Core</span></cite>]</p></dd>
1.29 avankest 294:
1.250 avankest 295: <dt>HTML5</dt>
1.161 avankest 296:
297: <dd>
1.189 avankest 298: <p>A <span>conforming user agent</span> <em class="ct">must</em> support
1.250 avankest 299: at least the subset of the functionality defined in HTML5 that
1.197 avankest 300: this specification relies upon, such as the basics of the
301: <code>Window</code> object and serializing a <code>Document</code>
302: object. [<cite><span>HTML5</span></cite>]</p>
1.161 avankest 303:
304: <p class="note">The
305: <a href="http://www.w3.org/TR/2006/WD-Window-20060407/">Window Object
306: 1.0</a> draft is not referenced normatively as it appears to be no
1.250 avankest 307: longer maintained and HTML5 defines the <code>Window</code> object in
308: more detail. This specification already depends on HTML5 for other
309: reasons so there is not much additional overhead because of this.</p>
1.161 avankest 310:
1.29 avankest 311: <dt>HTTP</dt>
1.33 avankest 312:
1.248 avankest 313: <dd><p>A <span title="conforming user agent">conforming user agent</span>
314: <em class="ct">must</em> support some version of the HTTP protocol.
315: Requirements regarding HTTP are made throughout the specification.
316: [<cite><span>RFC2616</span></cite>]</p></dd>
1.189 avankest 317:
1.181 avankest 318: <dt>Web IDL</dt>
1.203 avankest 319:
1.248 avankest 320: <dd><p>A <span>conforming user agent</span> <em class="ct">must</em> also
321: be a conforming implementation of the IDL fragments in this
322: specification, as described in the Web IDL specification.
1.181 avankest 323: [<cite><span>WebIDL</span></cite>]
1.248 avankest 324:
325:
1.29 avankest 326: </dl>
1.12 avankest 327:
1.157 avankest 328:
1.153 avankest 329: <h3 id="terminology">Terminology</h3>
1.209 avankest 330:
1.233 avankest 331: <p><dfn id="dfn-obtain-unicode">convert a DOMString to a sequence of Unicode characters</dfn>
332: is defined by the Web IDL specification.
333: [<cite><span>WebIDL</span></cite>]</p>
1.266 avankest 334:
335: <p>The term <dfn>user credentials</dfn> for the purposes of this
336: specification means cookies, HTTP authentication, and client-side SSL
337: certificates. Specifically it does not refer to proxy authentication or
338: the <code title="http-origin">Origin</code> header.
339: <a href="#ref-cookies">[COOKIES]</a> <!-- XXX ref? --></p>
1.248 avankest 340:
1.200 avankest 341: <p>The terms and algorithms
1.257 avankest 342: <dfn id="url-fragment"><code><fragment></code></dfn>,
343: <dfn id="url-scheme"><code><scheme></code></dfn>,
1.265 avankest 344: <dfn id="cookie-free-document-object">cookie-free <code>Document</code> object</dfn>,
1.203 avankest 345: <dfn id="document-base-url">document base URL</dfn>,
1.244 avankest 346: <dfn id="document-character-encoding">document's character encoding</dfn>,
1.205 avankest 347: <dfn id="event-handler-attributes-0">event handler attributes</dfn>,
1.203 avankest 348: <dfn id="event-handler-event-type">event handler event type</dfn>,
1.260 avankest 349: <dfn id="fetch">fetch</dfn>,
1.203 avankest 350: <dfn id="fully-active">fully active</dfn>,
1.206 avankest 351: <dfn id="function"><code>Function</code></dfn>,
1.225 avankest 352: <dfn id="dom-innerhtml" title="dom-innerHTML"><code>innerHTML</code></dfn>,
1.200 avankest 353: <dfn id="origin">origin</dfn>,
1.232 avankest 354: <dfn id="preferred-mime-name">preferred MIME name</dfn>,
1.203 avankest 355: <dfn id="resolve-a-url">resolve a URL</dfn>,
356: <dfn id="same-origin">same origin</dfn>,
357: <dfn id="storage-mutex">storage mutex</dfn>,
358: <dfn id="task">task</dfn>,
359: <dfn id="task-source">task source</dfn>,
1.252 avankest 360: <dfn id="task-queues">task queues</dfn>,
1.203 avankest 361: <dfn id="url">URL</dfn>,
1.232 avankest 362: <dfn id="url-character-encoding">URL character encoding</dfn>,
363: <dfn id="queue-a-task">queue a task</dfn>, and
364: <dfn id="valid-mime-type">valid MIME type</dfn>
1.250 avankest 365: are defined by the HTML5 specification.
1.157 avankest 366: [<cite><span>HTML5</span></cite>]</p>
1.210 avankest 367:
1.203 avankest 368: <p>The term <dfn id="entity-body">entity body</dfn> is used as described
369: in RFC 2616. <dfn id="method-token">Method token</dfn> is used as
370: described in section 5.1.1 of RFC 2616. <dfn><code>field-name</code></dfn>
371: and <dfn><code>field-value</code></dfn> are used as described in section
372: 4.2 of RFC 2616. [<cite><span>RFC2616</span></cite>]</p>
1.218 avankest 373:
1.258 avankest 374: <p>To <dfn>deflate a DOMString into a byte sequence</dfn> means to create
375: a sequence of bytes such that the <var title="">n</var>th byte of the
376: sequence is equal to the low-order byte of the <var title="">n</var>th
377: code point in the original DOMString.</p>
378:
379: <p>To <dfn>inflate a byte sequence into a DOMString</dfn> means to create
380: a DOMString such that the <var title="">n</var>th code point has 0x00 as
381: the high-order byte and the <var title="">n</var>th byte of the byte
382: sequence as the low-order byte.</p>
1.256 avankest 383:
1.203 avankest 384: <p><dfn><code>userinfo</code></dfn> is used as described in section 3.2.1
385: of RFC 3986. [<cite><span>RFC3986</span></cite>]</p>
386:
387: <p>To <dfn id="dispatch-readystatechange-event">dispatch a
388: <code>readystatechange</code> event</dfn> means that an event with the
1.273 avankest 389: name <code title="event-xhr-readystatechange">readystatechange</code>, which does not bubble and is not
1.232 avankest 390: cancelable, and which uses the <code>Event</code> interface, is to be
391: dispatched at the <code>XMLHttpRequest</code> object.</p>
1.80 avankest 392:
1.248 avankest 393:
394:
1.153 avankest 395: <h3 id="extensibility">Extensibility</h3>
1.12 avankest 396:
1.250 avankest 397: <p>User agents, Working Groups, and other interested parties are
398: <em>strongly encouraged</em> to discuss extensions on a relevant public
399: forum, preferably
400: <a href="mailto:public-webapps@w3.org">public-webapps@w3.org</a>. If this
401: is for some reason not possible prefix the extension in some way and start
402: the prefix with an uppercase letter. E.g. if company Foo wants to add a
403: private method <code>bar()</code> it could be named <code>FooBar()</code>
404: to prevent clashes with a potential future standardized
405: <code>bar()</code>.</p>
1.12 avankest 406:
1.153 avankest 407:
1.223 avankest 408: <h2>The <code title="">XMLHttpRequest</code> Interface</h2>
1.12 avankest 409:
1.58 avankest 410: <p>The <code>XMLHttpRequest</code> object can be used by scripts to
1.22 avankest 411: programmatically connect to their originating server via HTTP.</p>
1.12 avankest 412:
1.228 avankest 413: <pre class="idl">[NoInterfaceObject]
414: interface <dfn id="xmlhttprequesteventtarget">XMLHttpRequestEventTarget</dfn> : EventTarget {
415: // for future use
416: };
417:
1.240 avankest 418: [<span title="dom-XMLHttpRequest">Constructor</span>]
1.228 avankest 419: interface <dfn id="xmlhttprequest">XMLHttpRequest</dfn> : <span>XMLHttpRequestEventTarget</span> {
1.206 avankest 420: // <a href="#event-handler-attributes">event handler attributes</a>
1.273 avankest 421: attribute <span>Function</span> <span title="handler-xhr-onreadystatechange">onreadystatechange</span>;
1.58 avankest 422:
1.205 avankest 423: // <a href="#states">states</a>
1.272 avankest 424: const unsigned short <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> = 0;
425: const unsigned short <span title="dom-XMLHttpRequest-OPENED">OPENED</span> = 1;
426: const unsigned short <span title="dom-XMLHttpRequest-HEADERS_RECEIVED">HEADERS_RECEIVED</span> = 2;
427: const unsigned short <span title="dom-XMLHttpRequest-LOADING">LOADING</span> = 3;
428: const unsigned short <span title="dom-XMLHttpRequest-DONE">DONE</span> = 4;
1.277 avankest 429: readonly attribute unsigned short <span title="dom-XMLHttpRequest-readyState">readyState</span>;
1.58 avankest 430:
1.205 avankest 431: // <a href="#request">request</a>
1.274 avankest 432: void <span title="dom-XMLHttpRequest-open">open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>);
433: void <span title="dom-XMLHttpRequest-open">open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>, boolean <var>async</var>);
434: void <span title="dom-XMLHttpRequest-open">open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>, boolean <var>async</var>, DOMString? <var>user</var>);
435: void <span title="dom-XMLHttpRequest-open">open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>, boolean <var>async</var>, DOMString? <var>user</var>, DOMString? <var>password</var>);
1.279 ! avankest 436: void <span title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader</span>(DOMString <var>header</var>, DOMString <var>value</var>);
1.271 avankest 437: void <span title="dom-XMLHttpRequest-send">send</span>();
438: void <span title="dom-XMLHttpRequest-send">send</span>(Document <var>data</var>);
439: void <span title="dom-XMLHttpRequest-send">send</span>([AllowAny] DOMString? <var>data</var>);
1.275 avankest 440: void <span title="dom-XMLHttpRequest-abort">abort</span>();
1.58 avankest 441:
1.205 avankest 442: // <a href="#response">response</a>
1.276 avankest 443: readonly attribute unsigned short <span title="dom-XMLHttpRequest-status">status</span>;
444: readonly attribute DOMString <span title="dom-XMLHttpRequest-statusText">statusText</span>;
1.278 avankest 445: DOMString <span title="dom-XMLHttpRequest-getResponseHeader">getResponseHeader</span>(DOMString <var>header</var>);
446: DOMString <span title="dom-XMLHttpRequest-getAllResponseHeaders">getAllResponseHeaders</span>();
1.276 avankest 447: readonly attribute DOMString <span title="dom-XMLHttpRequest-responseText">responseText</span>;
448: readonly attribute Document <span title="dom-XMLHttpRequest-responseXML">responseXML</span>;
1.228 avankest 449: };</pre>
1.8 avankest 450:
1.235 avankest 451: <!-- XXX domintro boxes; HTML5-style -->
452:
1.124 avankest 453:
1.203 avankest 454: <h3>Origin and Base URL</h3>
455:
456: <p>Each <code>XMLHttpRequest</code> object has an associated
457: <dfn id="xmlhttprequest-origin"><code>XMLHttpRequest</code> origin</dfn>
458: and an
459: <dfn id="xmlhttprequest-base-url"><code>XMLHttpRequest</code> base URL</dfn>.
460:
461: <p>This specification defines their values when the global object is
462: represented by the <code>Window</code> object. When the
1.246 avankest 463: <code>XMLHttpRequest</code> object is used in other contexts their values
1.203 avankest 464: will have to be defined as appropriate for that context. That is
465: considered to be out of scope for this specification.</p>
466:
467: <p>In environments where the global object is represented by the
468: <code>Window</code> object the <code>XMLHttpRequest</code> object has an
469: associated
470: <dfn id="xmlhttprequest-document"><code>XMLHttpRequest</code> <code>Document</code></dfn>
471: which is the <code>Document</code> object associated with the
472: <code>Window</code> object for which the <code>XMLHttpRequest</code>
473: interface object was created.</p>
474:
475: <p class="note">The
476: <span><code>XMLHttpRequest</code> <code>Document</code></span> is used to
477: determine the <span><code>XMLHttpRequest</code> origin</span> and
478: <span><code>XMLHttpRequest</code> base URL</span> at a later stage.</p>
479:
480:
1.263 avankest 481:
1.203 avankest 482: <h3>Task Sources</h3>
1.218 avankest 483:
1.251 avankest 484: <p>The <span>task source</span> used by this specification is the
485: <dfn><code>XMLHttpRequest</code> task source</dfn>.</p>
1.203 avankest 486:
487:
1.211 avankest 488: <h3 id="constructors">Constructors</h3>
1.203 avankest 489:
1.263 avankest 490:
491:
1.270 avankest 492: <dl class="domintro">
493: <dt><var title="">client</var> = new <code title="dom-XMLHttpRequest">XMLHttpRequest</code>()</dt>
494: <dd>Returns a new <code>XMLHttpRequest</code> object.</dd>
495:
496: </dl>
497:
1.203 avankest 498: <p>When the
1.266 avankest 499: <dfn id="dom-xmlhttprequest" title="dom-XMLHttpRequest"><code>XMLHttpRequest()</code></dfn>
1.203 avankest 500: constructor is invoked, the user agent <em class="ct">must</em> return a
501: new <code>XMLHttpRequest</code> object.</p>
502:
1.263 avankest 503:
1.203 avankest 504:
1.205 avankest 505: <h3 id="event-handler-attributes">Event Handler Attributes</h3>
506:
1.248 avankest 507:
508:
1.205 avankest 509: <p>The following is the
510: <span title="event handler attributes">event handler attribute</span> (and
511: its corresponding <span>event handler event type</span>) that
512: <em class="ct">must</em> be supported as DOM attribute by the
513: <code>XMLHttpRequest</code> object:</p>
514:
515: <table>
516: <thead>
517: <tr>
518: <th><span title="event handler attributes">event handler attribute</span>
519: <th><span>event handler event type</span>
520: <tbody>
521: <tr>
1.273 avankest 522: <td><dfn id="handler-xhr-onreadystatechange" title="handler-xhr-onreadystatechange"><code>onreadystatechange</code></dfn>
523: <td><code title="event-xhr-readystatechange">readystatechange</code></td>
1.205 avankest 524: </table>
525:
526:
527: <h3 id="states">States</h3>
1.277 avankest 528:
529: <dl class="domintro">
530: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-readyState">readyState</code></dt>
531: <dd><p>Returns the current state.</p></dd>
532: </dl>
1.203 avankest 533:
534: <p>The <code>XMLHttpRequest</code> object can be in several states. The
1.277 avankest 535: <dfn id="dom-xmlhttprequest-readystate" title="dom-XMLHttpRequest-readyState"><code>readyState</code></dfn>
536: attribute <em class="ct">must</em> return the current state, which
1.203 avankest 537: <em class="ct">must</em> be one of the following values:</p>
538:
539: <dl>
1.272 avankest 540: <dt><dfn id="dom-xmlhttprequest-unsent" title="dom-XMLHttpRequest-UNSENT"><code>UNSENT</code></dfn>
1.203 avankest 541: (numeric value 0)</dt>
542: <dd><p>The object has been constructed.</p></dd>
543:
1.272 avankest 544: <dt><dfn id="dom-xmlhttprequest-opened" title="dom-XMLHttpRequest-OPENED"><code>OPENED</code></dfn>
1.203 avankest 545: (numeric value 1)</dt>
1.274 avankest 546: <dd><p>The <code title="dom-XMLHttpRequest-open">open()</code> method has been successfully invoked.
1.203 avankest 547: During this state request headers can be set using
1.279 ! avankest 548: <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>
! 549: and the request can be made using the
1.271 avankest 550: <code title="dom-XMLHttpRequest-send">send()</code> method.</p></dd>
1.203 avankest 551:
1.272 avankest 552: <dt><dfn id="dom-xmlhttprequest-headers_received" title="dom-XMLHttpRequest-HEADERS_RECEIVED"><code>HEADERS_RECEIVED</code></dfn>
1.203 avankest 553: (numeric value 2)</dt>
1.257 avankest 554: <dd><p>All redirects (if any) have been followed and all HTTP headers of
555: the final response have been received. Several response members of the
556: object are now available.</p></dd>
1.203 avankest 557:
1.272 avankest 558: <dt><dfn id="dom-xmlhttprequest-loading" title="dom-XMLHttpRequest-LOADING"><code>LOADING</code></dfn>
1.203 avankest 559: (numeric value 3)</dt>
560: <dd><p>The <span>response entity body</span> is being received.</p></dd>
561:
1.272 avankest 562: <dt><dfn id="dom-xmlhttprequest-done" title="dom-XMLHttpRequest-DONE"><code>DONE</code></dfn>
1.203 avankest 563: (numeric value 4)</dt>
564: <dd><p>The data transfer has been completed or something went wrong
565: during the transfer (e.g. infinite redirects).</p></dd>
566: </dl>
567:
1.272 avankest 568: <p>The <span title="dom-XMLHttpRequest-OPENED">OPENED</span> state has an associated
1.203 avankest 569: <dfn id="send-flag"><code>send()</code> flag</dfn> that indicates whether
1.271 avankest 570: the <code title="dom-XMLHttpRequest-send">send()</code> method has been
571: invoked. It can be either true or false and has an initial value of
572: false.</p>
1.203 avankest 573:
1.272 avankest 574: <p>The <span title="dom-XMLHttpRequest-DONE">DONE</span> state has an associated
1.203 avankest 575: <dfn id="error-flag">error flag</dfn> that indicates some type of network
576: error or abortion. It can be either true or false and has an initial value
577: of false.</p>
578:
579:
1.205 avankest 580: <h3 id="request">Request</h3>
1.203 avankest 581:
582: <p>The <code>XMLHttpRequest</code> object holds the following request
583: metadata variables:</p>
584:
1.204 avankest 585: <dl>
586: <dt>The <dfn>asynchronous flag</dfn></dt>
1.266 avankest 587: <dd>True when <span title="fetch">fetching</span> is done asychronously.
588: False when fetching is done synchronously.</dd>
1.204 avankest 589:
590: <dt>The <dfn>request method</dfn></dt>
591: <dd>The method used in the request.</dd>
592:
593: <dt>The <dfn>request URL</dfn></dt>
594: <dd>The <span>URL</span> used in the request.</dd>
1.218 avankest 595:
1.204 avankest 596: <dt>The <dfn>request username</dfn></dt>
597: <dd>The username used in the request or null if there is no
598: username.</dd>
1.218 avankest 599:
1.204 avankest 600: <dt>The <dfn>request password</dfn></dt>
601: <dd>The password used in the request or null if there is no
602: password.</dd>
1.218 avankest 603:
1.204 avankest 604: <dt>The <dfn id="author-request-headers">author request headers</dfn></dt>
605: <dd>A list consisting of HTTP header name/value pairs to be used in the
606: request.</p>
1.203 avankest 607:
1.204 avankest 608: <dt>The <dfn>request entity body</dfn></dt>
1.218 avankest 609: <dd>The <span>entity body</span> used in the request.</dd>
1.248 avankest 610:
611:
1.204 avankest 612: </dl>
1.203 avankest 613:
1.248 avankest 614:
615:
1.203 avankest 616:
617: <h4>The <code title="">open()</code> method</h4>
1.269 avankest 618:
619: <dl class="domintro">
1.274 avankest 620: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-open">open(<var title="">method</var>,
621: <var title="">url</var>, <var title="">async</var>, <var title="">user</var>,
622: <var title="">password</var>)</code></dt>
1.269 avankest 623:
624: <dd><p>Sets the <span>request method</span>, <span>request URL</span>,
625: <span>asynchronous flag</span>, <span>request username</span>, and
626: <span>request password</span>.</p></dd>
627: </dl>
1.88 avankest 628:
1.274 avankest 629: <p>When the
630: <dfn id="dom-xmlhttprequest-open" title="dom-XMLHttpRequest-open"><code>open(<var title="">method</var>, <var title="">url</var>, <var title="">async</var>, <var title="">user</var>, <var title="">password</var>)</code></dfn>
631: method is invoked, the user agent <em class="ct">must</em> run these steps
632: (unless otherwise indicated):</p>
1.90 avankest 633:
1.88 avankest 634: <ol>
1.203 avankest 635: <li>
636: <p>If the <code>XMLHttpRequest</code> object has an associated
637: <span><code>XMLHttpRequest</code> <code>Document</code></span> run
638: these substeps:</p>
1.90 avankest 639:
1.203 avankest 640: <ol>
641: <li><p>If the
642: <span><code>XMLHttpRequest</code> <code>Document</code></span> is not
643: <span>fully active</span> raise an <code>INVALID_STATE_ERR</code>
644: exception and terminate the overall set of steps.</p></li>
645:
646: <li><p>Let <span><code>XMLHttpRequest</code> base URL</span> be the
647: <span>document base URL</span> of the
648: <span><code>XMLHttpRequest</code> <code>Document</code></span>.</p></li>
649:
650: <li><p>Let <span><code>XMLHttpRequest</code> origin</span> be the
651: <span>origin</span> of the
652: <span><code>XMLHttpRequest</code> <code>Document</code></span>.</p></li>
653: </ol>
654: </li>
1.90 avankest 655:
1.256 avankest 656: <li><p>If any code point in <var>method</var> is higher than
657: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS or after
658: <span title="deflate a DOMString into an byte sequence">deflating</span>
659: <var>method</var> it does not match the
1.210 avankest 660: <span>Method token</span> production raise a <code>SYNTAX_ERR</code>
1.256 avankest 661: exception and terminate these steps. Otherwise let <var>method</var> be
662: the result of
663: <span title="deflate a DOMString into an byte sequence">deflating</span>
664: <var>method</var>.</p></li> <!-- This sounds lame, but it works. -->
1.118 avankest 665:
1.115 avankest 666: <li>
1.256 avankest 667: <p>If <var>method</var> is a case-insensitive match for
1.203 avankest 668: <code>CONNECT</code>, <code>DELETE</code>, <code>GET</code>,
669: <code>HEAD</code>, <code>OPTIONS</code>, <code>POST</code>,
670: <code>PUT</code>, <code>TRACE</code>, or <code>TRACK</code>
1.256 avankest 671: subtract 0x20 from each byte in the range 0x61 (ASCII a) to
672: 0x7A (ASCII z).</p>
1.118 avankest 673:
1.203 avankest 674: <p class="note">If it does not match any of the above, it is passed
675: through <em>literally</em>, including in the final request.</p>
1.115 avankest 676: </li>
1.203 avankest 677: <!-- WebKit (and supposedly Gecko) also uppercase: COPY, INDEX, LOCK,
678: M-POST, MKCOL, MOVE, PROPFIND, PROPPATCH, and UNLOCK. -->
1.118 avankest 679:
1.111 avankest 680: <li>
1.256 avankest 681: <p>If <var>method</var> is a case-sensitive match for
1.259 avankest 682: <code>CONNECT</code>, <code>TRACE</code>, or <code>TRACK</code> raise a
683: <code>SECURITY_ERR</code> exception and terminate these steps.</p>
1.117 avankest 684:
1.203 avankest 685: <p class="note">Allowing these methods poses a security risk.
686: [<cite><span>HTTPVERBSEC</span></cite>]</p>
1.111 avankest 687: </li>
688:
1.203 avankest 689: <li><p>Let <var title="">url</var> be a <span>URL</span>.</p></li>
690:
1.209 avankest 691: <li><p>Let <span>URL character encoding</span> of <var title="">url</var>
692: be UTF-8.</p></li>
1.113 avankest 693:
1.255 avankest 694: <li><p><span title="Resolve a URL">Resolve</span> <var title="">url</var>
1.203 avankest 695: relative to the <span><code>XMLHttpRequest</code> base URL</span>.
696: If the algorithm returns an error raise a <code>SYNTAX_ERR</code>
697: exception and terminate these steps.</p></li>
698:
699: <!-- Presto and Gecko override the encoding. WebKit does not. Trident
700: does not support non-ASCII URLs. This matters for the <query> component,
701: see HTML5. -->
702:
703: <li><p>Drop <code><fragment></code> from <var title="">url</var>.</p></li>
704:
705: <li><p>If <var title="">url</var> contains an unsupported <code><scheme></code>
706: raise a <code>NOT_SUPPORTED_ERR</code> and terminate these
707: steps.</p></li>
708:
709: <li><p>If the <code>"user:password"</code> format in the
710: <code>userinfo</code> production is not supported for the relevant scheme
711: and <var title="">url</var> contains this format raise a
712: <code>SYNTAX_ERR</code> and terminate these steps.</p></li>
713:
714: <li><p>If <var title="">url</var> contains the <code>"user:password"</code>
715: format let <var>temp user</var> be the user part and
716: <var>temp password</var> be the password part.</p></li>
717:
718: <li><p>If <var title="">url</var> just contains the <code>"user"</code>
719: format let <var>temp user</var> be the user part.</p></li>
720:
1.248 avankest 721:
1.203 avankest 722: <li><p>If the <span>origin</span> of <var title="">url</var> is not
723: <span>same origin</span> with the
1.259 avankest 724: <span><code>XMLHttpRequest</code> origin</span> raise a
725: <code>SECURITY_ERR</code> exception and terminate these steps.</p></li>
1.248 avankest 726:
727:
1.203 avankest 728:
1.211 avankest 729: <li><p>Let <var>async</var> be the value of the <var>async</var> argument
1.266 avankest 730: or true if it was omitted.</p></li>
1.203 avankest 731:
732: <li>
733: <p>If the <var>user</var> argument was not omitted follow these sub
734: steps:</p>
1.90 avankest 735:
1.203 avankest 736: <ol>
1.263 avankest 737:
738:
1.203 avankest 739: <li><p>If the syntax of <var>user</var> does not match the syntax
740: specified by the relevant authentication scheme, raise a
741: <code>SYNTAX_ERR</code> exception and terminate the overall set of
742: steps.</p></li>
1.163 avankest 743:
1.239 avankest 744: <li><p>If <var>user</var> is null let <var>temp user</var>
1.203 avankest 745: be null.</p></li>
1.90 avankest 746:
1.203 avankest 747: <li><p>Otherwise let <var>temp user</var> be <var>user</var>.</p></li>
748: </ol>
1.88 avankest 749:
1.203 avankest 750: <p class="note">These steps override anything that may have been set by
751: the <var title="">url</var> argument.</p>
752: </li>
1.88 avankest 753:
1.128 avankest 754: <li>
1.203 avankest 755: <p>If the <var>password</var> argument was not omitted follow these sub
756: steps:</p>
757:
758: <ol>
1.263 avankest 759:
760:
1.203 avankest 761: <li><p>If the syntax of <var>password</var> does not match the syntax
762: specified by the relevant authentication scheme, raise a
763: <code>SYNTAX_ERR</code> exception and terminate the overall set of
764: steps.</p></li>
1.167 avankest 765:
1.239 avankest 766: <li><p>If <var>password</var> is null let
1.203 avankest 767: <var>temp password</var> be null.</p></li>
768:
769: <li><p>Otherwise let <var>temp password</var> be
770: <var>password</var>.</p></li>
771: </ol>
772:
773: <p class="note">These steps override anything that may have been set by
774: the <var title="">url</var> argument.</p>
1.128 avankest 775: </li>
1.88 avankest 776:
1.203 avankest 777: <li><p><span title="abort send()">Abort the <code>send()</code> algorithm</span>.</p></li>
778:
779: <li><p>The user agent <em class="ct">should</em> cancel any network
780: activity for which the object is responsible.</p></li>
781: <!-- we can hardly require it... -->
782:
1.252 avankest 783: <li><p>If there are any <span title="task">tasks</span> from the object's
784: <span><code>XMLHttpRequest</code> task source</span> in one of the
785: <span>task queues</span>, then remove those tasks.</p></li>
786:
1.203 avankest 787: <li>
788: <p>Set variables associated with the object as follows:</p>
789:
790: <ul>
791: <li><p>Set the <span><code>send()</code> flag</span> to false.</p></li>
792:
793: <li><p>Set <span>response entity body</span> to null.</p></li>
794:
795: <li><p>Empty the list of <span>author request headers</span>.</p>
796:
797: <li><p>Set the <span>request method</span> to <var>method</var>.</p></li>
798:
799: <li><p>Set the <span>request URL</span> to <var title="">url</var>.</p></li>
1.58 avankest 800:
1.203 avankest 801: <li><p>Set the <span>request username</span> to <var>temp user</var>.</p></li>
1.12 avankest 802:
1.203 avankest 803: <li><p>Set the <span>request password</span> to <var>temp password</var>.</p></li>
1.12 avankest 804:
1.266 avankest 805: <li><p>Set the <span>asynchronous flag</span> to the value of
806: <var>async</var>.</p></li>
1.203 avankest 807: </ul>
808: </li>
1.58 avankest 809:
1.203 avankest 810: <li><p>Switch the the state to
1.272 avankest 811: <span title="dom-XMLHttpRequest-OPENED">OPENED</span>.</p></li>
1.58 avankest 812:
1.203 avankest 813: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
814: </ol>
1.248 avankest 815:
816:
1.203 avankest 817: <p class="note">A future version or extension of this specification will
818: define a way of doing cross-origin requests.</p>
1.248 avankest 819:
1.58 avankest 820:
1.14 avankest 821:
1.203 avankest 822: <h4>The <code title="">setRequestHeader()</code> method</h4>
1.12 avankest 823:
1.270 avankest 824: <dl class="domintro">
1.279 ! avankest 825: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader(<var title="">header</var>, <var title="">value</var>)</code></dt>
1.270 avankest 826:
827: <dd>
828: <p>Appends an header to the list of
829: <span>author request headers</span> or if the header is already in the
830: <span>author request headers</span> its value appended to.</p>
831: <!-- XXX should mention when it throws? -->
832: </dd>
833: </dl>
1.45 avankest 834:
1.279 ! avankest 835: <p class="note">As indicated in the algorithm below certain headers cannot
! 836: be set and are left up to the user agent. In addition there are certain
! 837: other headers the user agent will take control of if they are not set by
! 838: the author as indicated at the end of the
1.271 avankest 839: <code title="dom-XMLHttpRequest-send">send()</code> method section.</p>
1.203 avankest 840:
1.248 avankest 841:
842:
1.203 avankest 843: <p>When the
1.279 ! avankest 844: <dfn id="dom-xmlhttprequest-setrequestheader" title="dom-XMLHttpRequest-setRequestHeader"><code>setRequestHeader(<var title="">header</var>, <var title="">value</var>)</code></dfn>
! 845: method is invoked, the user agent <em class="ct">must</em> run these
! 846: steps:</p>
1.14 avankest 847:
1.203 avankest 848: <ol>
1.272 avankest 849: <li><p>If the state is not <span title="dom-XMLHttpRequest-OPENED">OPENED</span> raise
1.203 avankest 850: an <code>INVALID_STATE_ERR</code> exception and terminate these
851: steps.</p></li>
852:
853: <li><p>If the <span><code>send()</code> flag</span> is true raise an
854: <code>INVALID_STATE_ERR</code> exception and terminate these
855: steps.</p></li>
856:
1.256 avankest 857: <li><p>If any code point in <var>header</var> is higher than
858: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS or after
859: <span title="deflate a DOMString into an byte sequence">deflating</span>
860: <var>header</var> it does not match the
861: <span>field-name</span> production raise a <code>SYNTAX_ERR</code>
862: exception and terminate these steps. Otherwise let <var>header</var> be
863: the result of
864: <span title="deflate a DOMString into an byte sequence">deflating</span>
865: <var>header</var>.</p></li> <!-- This sounds lame, but it works. -->
1.203 avankest 866:
867: <li>
1.256 avankest 868: <p>If any code point in <var>value</var> is higher than
869: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS or after
870: <span title="deflate a DOMString into an byte sequence">deflating</span>
871: <var>value</var> it does not match the
872: <span>field-value</span> production raise a <code>SYNTAX_ERR</code>
873: exception and terminate these steps. Otherwise let <var>value</var> be
874: the result of
875: <span title="deflate a DOMString into an byte sequence">deflating</span>
876: <var>value</var>.</p> <!-- This sounds lame, but it works. -->
1.203 avankest 877:
878: <p class="note">The empty string is legal and represents the empty
879: header value.</p>
880: </li>
881:
882: <li>
1.259 avankest 883: <p>Terminate these steps if <var>header</var> is a case-insensitive
884: match for one of the following headers:</p>
1.203 avankest 885:
886: <ul>
887: <li><code>Accept-Charset</code></li>
888: <li><code>Accept-Encoding</code></li>
889: <li><code>Connection</code></li>
890: <li><code>Content-Length</code></li>
891: <li><code>Cookie</code></li>
892: <li><code>Cookie2</code></li>
893: <li><code>Content-Transfer-Encoding</code></li>
894: <li><code>Date</code></li>
895: <li><code>Expect</code></li>
896: <li><code>Host</code></li>
897: <li><code>Keep-Alive</code></li>
898: <li><code>Referer</code></li>
899: <li><code>TE</code></li>
900: <li><code>Trailer</code></li>
901: <li><code>Transfer-Encoding</code></li>
902: <li><code>Upgrade</code></li>
903: <li><code>User-Agent</code></li>
904: <li><code>Via</code></li>
905: </ul>
1.96 avankest 906:
1.256 avankest 907: <p>… or if the start of <var>header</var> is a case-insensitive
908: match for <code>Proxy-</code> or <code>Sec-</code> (including when
909: <var>header</var> is just <code>Proxy-</code> or <code>Sec-</code>).</p>
1.203 avankest 910:
911: <p class="note">The above headers are not allowed to be set as they are
912: better controlled by the user agent as it knows best what value they
1.259 avankest 913: ought to have. Header names starting with <code>Sec-</code> are not
1.203 avankest 914: allowed to be set to allow new headers to be minted in the future that
915: are guaranteed not to come from <code>XMLHttpRequest</code>. (Older
916: clients would however still be vulnerable as they allow such headers to
917: be set.)</p>
918: </li>
1.14 avankest 919:
1.203 avankest 920: <li><p>If <var>header</var> is not in the
921: <span>author request headers</span> list append <var>header</var> with
922: its associated <var>value</var> to the list and terminate these
923: steps.</p></li>
924:
925: <li><p>If <var>header</var> is in the <span>author request headers</span>
926: list either use multiple headers, combine the values or use a combination
927: of those (section 4.2, RFC 2616).
928: [<cite><span>RFC2616</span></cite>]</p></li>
929: <!-- XXX it seems UAs always combine the values -->
930: </ol>
1.45 avankest 931:
1.271 avankest 932: <p class="note">See also the
933: <code title="dom-XMLHttpRequest-send">send()</code> method regarding user
1.203 avankest 934: agent header handling for caching, authentication, proxies, and
935: cookies.</p>
1.14 avankest 936:
1.203 avankest 937: <div class="example">
938: <pre><code>// The following script:
1.14 avankest 939: var client = new XMLHttpRequest();
940: client.open('GET', 'demo.cgi');
941: client.setRequestHeader('X-Test', 'one');
942: client.setRequestHeader('X-Test', 'two');
943: client.send();
944:
945: // ...would result in the following header being sent:
946: ...
947: X-Test: one, two
1.58 avankest 948: ...</code></pre>
1.203 avankest 949: </div>
1.255 avankest 950:
1.248 avankest 951:
1.218 avankest 952:
1.203 avankest 953:
954: <h4>The <code title="">send()</code> method</h4>
1.12 avankest 955:
1.271 avankest 956: <dl class="domintro">
957: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-send">send(<var title="">data</var>)</code></dt>
958: <dd><p>Initiates the request. The optional argument provides the
959: <span>request entity body</span>.</p></dd>
960: </dl>
961: <!-- XXX throws?! -->
1.203 avankest 962:
963: <p>When the
1.271 avankest 964: <dfn id="dom-xmlhttprequest-send" title="dom-XMLHttpRequest-send"><code>send(<var>data</var>)</code></dfn>
1.203 avankest 965: method is invoked, the user agent <em class="ct">must</em> run the
966: following steps (unless otherwise noted). This algorithm gets aborted when
1.275 avankest 967: the <code title="dom-XMLHttpRequest-open">open()</code> or <code title="dom-XMLHttpRequest-abort">abort()</code> method is invoked. When
1.203 avankest 968: the
969: <dfn title="abort send()" id="abort-send-algorithm"><code>send()</code> algorithm is aborted</dfn>
970: the user agent <em class="ct">must</em> terminate the algorithm after
971: finishing the step it is on.</p>
972:
973: <p class="note">The <code title="">send()</code> algorithm can only be
974: aborted when the <span>asynchronous flag</span> is true and only after the
975: method call has returned.</p>
1.181 avankest 976:
1.203 avankest 977: <ol>
1.272 avankest 978: <li><p>If the state is not <span title="dom-XMLHttpRequest-OPENED">OPENED</span> raise
1.203 avankest 979: an <code>INVALID_STATE_ERR</code> exception and terminate these
980: steps.</p></li>
981:
982: <li><p>If the <span><code>send()</code> flag</span> is true raise an
983: <code>INVALID_STATE_ERR</code> exception and terminate these
984: steps.</p></li>
1.58 avankest 985:
1.203 avankest 986: <li>
987: <p>If the <span>request method</var> is <code>GET</code> or
1.239 avankest 988: <code>HEAD</code> act as if <var>data</var> is null.</p>
1.232 avankest 989:
990: <p>If the <var>data</var> argument has been omitted or is
1.239 avankest 991: null, do not include a <span>request entity body</span>
1.232 avankest 992: and go to the next step.</p>
1.248 avankest 993:
994: <p>Otherwise, let <var>encoding</var> be null, <var>mime type</var> be
995: null, and then follow these rules:</p>
1.203 avankest 996:
997: <dl class="switch">
1.248 avankest 998:
999:
1000: <dt>If <var>data</var> is a <code>Document</code>
1.203 avankest 1001:
1002: <dd>
1.232 avankest 1003: <p>Let <var>encoding</var> be the <span>preferred MIME name</span> of
1004: the
1005: <span title="document's character encoding">character encoding</span>
1006: of <var>data</var>. If <var>encoding</var> is UTF-16 change it to
1007: UTF-8.</p>
1008:
1.248 avankest 1009: <p>Let <var>mime type</var> be "<code>application/xml;charset=</code>"
1010: followed by <var>encoding</var>.</p>
1.232 avankest 1011:
1012: <p>Let the <span>request entity body</span> be the result of getting
1013: the <code title="dom-innerHTML">innerHTML</code> attribute on
1.233 avankest 1014: <var>data</var>
1015: <span title="convert a DOMString to a sequence of Unicode characters">converted to Unicode</span>
1016: and encoded as <var>encoding</var>. Re-raise any exception this
1017: raises.</p>
1.218 avankest 1018:
1.233 avankest 1019: <p class="note">In particular, if the document cannot be serialized an
1.217 avankest 1020: <code>INVALID_STATE_ERR</code> exception is raised.</p>
1021:
1.203 avankest 1022: <p class="note">Subsequent changes to the <code>Document</code> have
1023: no effect on what is submitted.</p>
1024: </dd>
1.237 avankest 1025:
1.248 avankest 1026: <dt>If <var>data</var> is a <code>DOMString</code></dt>
1.237 avankest 1027:
1.248 avankest 1028: <dd>
1029: <p>Let <var>encoding</var> be UTF-8.</p>
1030:
1031: <p>Let <var>mime type</var> be "<code>text/plain;charset=UTF-8</code>".</p>
1032:
1033: <p>Let the <span>request entity body</span> be <var>data</var>
1034: <span title="convert a DOMString to a sequence of Unicode characters">converted to Unicode</span>
1035: and encoded as UTF-8.</p>
1036: </dd>
1037:
1038:
1.203 avankest 1039: </dl>
1.58 avankest 1040:
1.232 avankest 1041: <p>If a <code>Content-Type</code> header is set using
1.279 ! avankest 1042: <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>
! 1043: whose value is a <span>valid MIME type</span> and has a
! 1044: <code>charset</code> parameter whose value is not a case-insensitive
! 1045: match for <var title="">encoding</var>, and <var title="">encoding</var>
! 1046: is not null, set all the <code>charset</code> parameters of the
! 1047: <code>Content-Type</code> header to <var title="">encoding</var>.</p>
1.232 avankest 1048:
1049: <p>If no <code>Content-Type</code> header has been set using
1.279 ! avankest 1050: <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>
! 1051: and <var title="">mime type</var> is not null set a
! 1052: <code>Content-Type</code> request header with as value
! 1053: <var title="">mime type</var>.</p>
1.236 avankest 1054:
1055: <!-- reminder: if we ever change this to always include charset it has
1056: to be included as the first parameter for compatibility reasons -->
1.203 avankest 1057: </li>
1.202 avankest 1058:
1.203 avankest 1059: <li><p>If the <span>asynchronous flag</span> is false release the
1060: <span>storage mutex</span>.</p></li>
1.103 avankest 1061:
1.248 avankest 1062:
1063:
1.203 avankest 1064: <li><p>Set the <span>error flag</span> to false.</p></li>
1.218 avankest 1065:
1.248 avankest 1066:
1067:
1.211 avankest 1068: <li>
1069: <p>If the <span>asynchronous flag</span> is true run these substeps:</p>
1.218 avankest 1070:
1.211 avankest 1071: <ol>
1.217 avankest 1072: <li><p>Set the <span><code>send()</code> flag</span> to true.</p></li>
1073:
1.211 avankest 1074: <li>
1075: <p><span>Dispatch a <code>readystatechange</code> event</span>.</p>
1.145 avankest 1076:
1.211 avankest 1077: <p class="note">The state does not change. The event is dispatched for
1078: historical reasons.</p>
1079: </li>
1080:
1.248 avankest 1081:
1082:
1.271 avankest 1083: <li><p>Return the <code title="dom-XMLHttpRequest-send">send()</code>
1084: method call, but continue running the steps in this algorithm.</p></li>
1.211 avankest 1085: </ol>
1086: </li>
1.218 avankest 1087:
1.203 avankest 1088: <li>
1.248 avankest 1089:
1.211 avankest 1090:
1.261 avankest 1091: <p><span>Fetch</span> the <span>request URL</span> from
1.260 avankest 1092: <i title="">origin</i>
1093: <span><code>XMLHttpRequest</code> origin</span>, with the
1094: <i title="">synchronous flag</i> set if the
1095: <span>asynchronous flag</span> is false, using HTTP method
1.248 avankest 1096: <span>request method</span>, user <span>request username</span> (if
1097: non-null) and password <span>request password</span> (if non-null),
1098: taking into account the <span>request entity body</span>, list of
1099: <span>author request headers</span> and the rules listed at the end of
1100: this section.</p>
1101:
1102: <dl class="switch">
1103: <dt>If the <span>asynchronous flag</span> is false</dt>
1104: <dd>
1105: <p>While making the request also follow the
1106: <span>same-origin request event rules</span>.</p>
1107:
1108: <!--
1109: This cannot involve any task queue whatsoever because that would
1110: mean other tasks on the task queue might get processed as well
1111: which is counter to the whole idea of doing things synchronous.
1112: -->
1113:
1.271 avankest 1114: <p class="note">The
1115: <code title="dom-XMLHttpRequest-send">send()</code> method call will
1116: now be returned by virtue of this algorithm ending.</p>
1.248 avankest 1117: </dd>
1118:
1119: <dt>If the <span>asynchronous flag</span> is true</dt>
1120: <dd>
1121: <p><span>Make progress notifications</span>.</p>
1122:
1123: <p><span>Make upload progress notifications</span>.</p>
1124:
1125: <p>While processing the request, as data becomes available and when
1126: the user interferes with the request,
1.255 avankest 1127: <span title="queue a task">queue tasks</span> to update the
1128: <span>response entity body</span> and follow the
1.254 avankest 1129: <span>same-origin request event rules</span>.</p>
1.248 avankest 1130: </dd>
1131: </dl>
1132:
1.203 avankest 1133: </li>
1134: </ol>
1.60 avankest 1135:
1.203 avankest 1136: <hr>
1137:
1.227 avankest 1138: <p>If the user agent allows the end user to configure a proxy it
1.248 avankest 1139: <em class="ct">should</em> modify the request appropriately; i.e., connect
1140: to the proxy host instead of the origin server, modify the
1141: <code>Request-Line</code> and send <code>Proxy-Authorization</code>
1142: headers as specified.</p>
1.262 avankest 1143:
1144: <hr>
1.212 avankest 1145:
1.218 avankest 1146: <p>If the user agent supports HTTP Authentication and
1.262 avankest 1147: <code title="http-authorization">Authorization</code> is not in the list
1148: of <span>author request headers</span>, it <em class="ct">should</em>
1.218 avankest 1149: consider requests originating from the <code>XMLHttpRequest</code> object
1150: to be part of the protection space that includes the accessed URIs and
1.262 avankest 1151: send <code title="http-authorization">Authorization</code> headers and
1152: handle <code>401 Unauthorized</code> requests appropriately.</p>
1153:
1154: <p>If authentication fails,
1155: <code title="http-authorization">Authorization</code> is not in the list
1156: of <span>author request headers</span>, <span>request username</span> is
1157: null, and <span>request password</span> is null, user agents
1158: <em class="ct">should</em> prompt the end user for their username and
1159: password.</p>
1160:
1161: <p>If authentication fails,
1162: <code title="http-authorization">Authorization</code> is not in the list
1163: of <span>author request headers</span>, <span>request username</span> is
1164: non-null, and <span>request password</span> is non-null, user agents
1165: <em class="ct">must not</em> prompt the end user for their username and
1166: password. [<cite><span>RFC2617</span></cite>]</p>
1.212 avankest 1167:
1.266 avankest 1168: <p class="note">End users are not prompted if username/password are
1.274 avankest 1169: provided through the <code title="dom-XMLHttpRequest-open">open()</code> API so that authors can implement
1.266 avankest 1170: their own user interface.</p>
1.262 avankest 1171:
1172: <hr>
1.212 avankest 1173:
1174: <p>If the user agent supports HTTP State Management it
1175: <em class="ct">should</em> persist, discard and send cookies (as received
1176: in the <code>Set-Cookie</code> and <code>Set-Cookie2</code> response
1177: headers, and sent in the <code>Cookie</code> header) as applicable.
1178: [<cite><span>COOKIES</span></cite>]</p>
1.262 avankest 1179:
1180: <hr>
1.212 avankest 1181:
1182: <p>If the user agent implements a HTTP cache it <em class="ct">should</em>
1.248 avankest 1183: respect <code>Cache-Control</code> request headers set by the
1.279 ! avankest 1184: <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>
! 1185: (e.g., <code>Cache-Control: no-cache</code> bypasses the cache). It
! 1186: <em class="ct">must not</em> send <code>Cache-Control</code> or
! 1187: <code>Pragma</code> request headers automatically unless the end user
! 1188: explicitly requests such behavior (e.g. by reloading the page).</p>
1.212 avankest 1189:
1190: <p>For <code>304 Not Modified</code> responses that are a result of a
1191: user agent generated conditional request the user agent
1192: <em class="ct">must</em> act as if the server gave a <code>200 OK</code>
1193: response with the appropriate content. The user agent
1.279 ! avankest 1194: <em class="ct">must</em> allow
! 1195: <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>
! 1196: to override automatic cache validation by setting request headers (e.g.
1.248 avankest 1197: <code>If-None-Match</code> or <code>If-Modified-Since</code>), in which
1.212 avankest 1198: case <code>304 Not Modified</code> responses <em class="ct">must</em> be
1199: passed through. [<cite><span>RFC2616</span></cite>]</p>
1.262 avankest 1200:
1201: <hr>
1.212 avankest 1202:
1203: <p>If the user agent implements server-driven content-negotiation
1204: it <em class="ct">should</em> set <code>Accept-Encoding</code> and
1.231 avankest 1205: <code>Accept-Charset</code> headers as appropriate. For
1206: <code>Accept</code> and <code>Accept-Language</code> the user agent
1207: <em class="ct">must</em> follow these constraints:</p>
1208:
1209: <ul>
1210: <li><p>Both headers <em class="ct">must not</em> be modified if they are
1.279 ! avankest 1211: already set through
! 1212: <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>.</p></li>
1.255 avankest 1213:
1.279 ! avankest 1214: <li><p>If not set through
! 1215: <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>
1.255 avankest 1216: <code>Accept-Language</code> <em class="ct">should</em> be set as
1.231 avankest 1217: appropriate.</p></li>
1218:
1.279 ! avankest 1219: <li><p>If not set through
! 1220: <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>
1.231 avankest 1221: <code>Accept</code> <em class="ct">must</em> be set with as value
1222: <code>*/*</code>.</p></li>
1223: </ul>
1224:
1225: <p>Responses <em class="ct">must</em> have the content-encodings
1226: automatically decoded. [<cite><span>RFC2616</span></cite>]</p>
1.212 avankest 1227:
1.262 avankest 1228: <hr>
1229:
1.212 avankest 1230: <p>Besides the <span>author request headers</span> user agents
1231: <em class="ct">should not</em> include additional request headers other
1.248 avankest 1232: than those mentioned above or other than those authors are not allowed to
1.279 ! avankest 1233: set using
! 1234: <code title="dom-XMLHttpRequest-setRequestHeader">setRequestHeader()</code>.
! 1235: This ensures that authors have a reasonably predictable API.</p>
1.218 avankest 1236:
1.212 avankest 1237:
1238: <h4>Infrastructure for the <code title="">send()</code> method</h4>
1.216 avankest 1239:
1.219 avankest 1240: <p>The <dfn>same-origin request event rules</dfn> are as follows:</p>
1.118 avankest 1241:
1.203 avankest 1242: <dl class="switch">
1243: <dt>If the response is an HTTP redirect</dt>
1244: <dd>
1.248 avankest 1245:
1.257 avankest 1246: <p>If the <span>origin</span> of the <span>URL</span> conveyed by the
1247: <code title="http-location">Location</code> header is
1248: <span>same origin</span> with the
1249: <span><code>XMLHttpRequest</code> origin</span> and the redirect does
1250: not violate infinite loop precautions, transparently follow the redirect
1251: while observing the <span>same-origin request event rules</span>.</p>
1.248 avankest 1252:
1253: <p>Otherwise, this is a <span>network error</span>.</p>
1254:
1255:
1.203 avankest 1256:
1257: <p class="note">HTTP places requirements on the user agent regarding the
1.204 avankest 1258: preservation of the <span>request method</span> and
1.248 avankest 1259: <span>request entity body</span> during redirects, and also requires end
1260: users to be notified of certain kinds of automatic redirections.</p>
1.203 avankest 1261: <!-- XXX HTTP needs fixing here -->
1.213 avankest 1262: </dd>
1.121 avankest 1263:
1.227 avankest 1264: <dt>If the end user cancels the download</dt>
1.213 avankest 1265: <dd><p>This is an <span>abort error</span>.</p></dd>
1.60 avankest 1266:
1.214 avankest 1267: <dt>In case of network errors</dt>
1.213 avankest 1268: <dd>
1269: <p>In case of DNS errors, TLS negotiation failure, or other type of
1270: network errors, this is a <span>network error</span>. Do not request any
1.227 avankest 1271: kind of end user interaction.</p>
1.121 avankest 1272:
1.213 avankest 1273: <p class="note">This does not include HTTP responses that indicate
1274: some type of error, such as HTTP status code 410.</p>
1275: </dd>
1.60 avankest 1276:
1.248 avankest 1277:
1278:
1.213 avankest 1279: <dt>Once all HTTP headers have been received and the
1.257 avankest 1280: <span>asynchronous flag</span> is true (and this is not an HTTP
1281: redirect)</dt>
1.272 avankest 1282: <dd><p><span>Switch to the dom-XMLHttpRequest-HEADERS_RECEIVED</span>.</p></dd>
1.186 avankest 1283:
1.220 avankest 1284: <dt>Once the first byte (or more) of the
1285: <span>response entity body</span> has been received and the
1286: <span>asynchronous flag</span> is true</dt>
1287: <dt>If there is no <span>response entity body</span> and the
1.213 avankest 1288: <span>asynchronous flag</span> is true</dt>
1.272 avankest 1289: <dd><p><span>Switch to the dom-XMLHttpRequest-LOADING</span>.</p></dd>
1.220 avankest 1290:
1291: <dt>Once the whole <span>response entity body</span> has been
1292: received</dt>
1.224 avankest 1293: <dt>If there is no <span>response entity body</span> and the
1294: <span>asynchronous flag</span> is false or the state is
1.272 avankest 1295: <span title="dom-XMLHttpRequest-LOADING">LOADING</span></dt>
1296: <dd><p><span>Switch to the dom-XMLHttpRequest-DONE</span>.</p></dd>
1.213 avankest 1297: </dl>
1.218 avankest 1298:
1.248 avankest 1299:
1300:
1.213 avankest 1301: <hr>
1.218 avankest 1302:
1.241 avankest 1303: <p>When something is said to be a <dfn>network error</dfn> run the
1304: <span>request error</span> steps for exception
1305: <code>NETWORK_ERR</code>.</p>
1306:
1307: <p>When something is said to be an <dfn>abort error</dfn> run the
1308: <span>request error</span> steps for exception
1309: <code>ABORT_ERR</code>.</p>
1.60 avankest 1310:
1.248 avankest 1311:
1312:
1.242 avankest 1313: <p>When something is said to be a <dfn>request error</dfn> for
1.248 avankest 1314: exception <var>exception</var> run these
1315: steps:</p>
1.12 avankest 1316:
1.213 avankest 1317: <ol>
1.254 avankest 1318: <li><p>The user agent <em class="ct">should</em> cancel any network
1319: activity for which the object is responsible.</p></li>
1320:
1321: <li><p>If there are any <span title="task">tasks</span> from the object's
1322: <span><code>XMLHttpRequest</code> task source</span> in one of the
1323: <span>task queues</span>, then remove those tasks.</p></li>
1.250 avankest 1324:
1.213 avankest 1325: <li><p>Set the <span>response entity body</span> to null.</p></li>
1.203 avankest 1326:
1.254 avankest 1327: <li><p>Empty the list of <span>author request headers</span>.</p></li>
1328:
1.213 avankest 1329: <li><p>Set the the <span>error flag</span> to true.</p></li>
1.12 avankest 1330:
1.272 avankest 1331: <li><p>Switch the state to <span title="dom-XMLHttpRequest-DONE">DONE</span>.</p></li>
1.203 avankest 1332:
1.241 avankest 1333: <li><p>If the <span>asynchronous flag</span> is false raise an
1334: <var>exception</var> exception and terminate the overall set of
1.213 avankest 1335: steps.</p></li>
1.203 avankest 1336:
1.248 avankest 1337: <li>
1.249 avankest 1338: <p><span>Dispatch a <code>readystatechange</code> event</span>.</p>
1.248 avankest 1339:
1340: <p class="note">At this point it is clear that the
1341: <span>asynchronous flag</span> is true.</p>
1342: </li>
1343:
1344:
1.203 avankest 1345:
1.248 avankest 1346: <li><p>Terminate the overall algorithm.</p></li>
1.213 avankest 1347: </ol>
1.203 avankest 1348:
1.248 avankest 1349:
1350: <p class="note">A future version of this specification will dispatch an
1.273 avankest 1351: <code title="event-xhr-error">error</code>/<code>abort</code> event here as well. (Depending on
1.248 avankest 1352: the type of error.)</p>
1353:
1.203 avankest 1354:
1.213 avankest 1355: <hr>
1.203 avankest 1356:
1.213 avankest 1357: <p>When it is said to
1.272 avankest 1358: <dfn id="switch-headers-received">switch to the dom-XMLHttpRequest-HEADERS_RECEIVED</dfn>
1.213 avankest 1359: run these steps:</p>
1.203 avankest 1360:
1.213 avankest 1361: <ol>
1.272 avankest 1362: <li><p>Switch the state to <span title="dom-XMLHttpRequest-HEADERS_RECEIVED">HEADERS_RECEIVED</span>.</p></li>
1.203 avankest 1363:
1.249 avankest 1364: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.213 avankest 1365: </ol>
1.218 avankest 1366:
1.213 avankest 1367: <p>When it is said to
1.272 avankest 1368: <dfn id="switch-loading">switch to the dom-XMLHttpRequest-LOADING</dfn> run these
1.213 avankest 1369: steps:</p>
1.218 avankest 1370:
1.213 avankest 1371: <ol>
1.272 avankest 1372: <li><p>Switch the state to <span title="dom-XMLHttpRequest-LOADING">LOADING</span>.</p></li>
1.203 avankest 1373:
1.249 avankest 1374: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.213 avankest 1375: </ol>
1.218 avankest 1376:
1.216 avankest 1377: <p>When it is said to
1.272 avankest 1378: <dfn id="switch-done">switch to the dom-XMLHttpRequest-DONE</dfn> run these steps:</p>
1.218 avankest 1379:
1.216 avankest 1380: <ol>
1.255 avankest 1381: <li><p>If the <span>asynchronous flag</span> is false update the
1382: <span>response entity body</span>.</p></li>
1383:
1.272 avankest 1384: <li><p>Switch the state to <span title="dom-XMLHttpRequest-DONE">DONE</span>.</p></li>
1.216 avankest 1385:
1.248 avankest 1386: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1387:
1.220 avankest 1388:
1.216 avankest 1389: </ol>
1.218 avankest 1390:
1.248 avankest 1391:
1392:
1.203 avankest 1393:
1394: <h4>The <code title="">abort()</code> method</h4>
1.275 avankest 1395:
1396: <dl class="domintro">
1397: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-abort">abort()</code></dt>
1398: <dd>Cancels any network activity.</dd>
1399: </dl>
1.203 avankest 1400:
1.275 avankest 1401: <p>When the
1402: <dfn id="dom-xmlhttprequest-abort" title="dom-XMLHttpRequest-abort"><code>abort()</code></dfn>
1403: method is invoked, the user agent <em class="ct">must</em> run these steps
1404: (unless otherwise noted):</p>
1.12 avankest 1405:
1.203 avankest 1406: <ol>
1407: <li><p><span title="abort send()">Abort the <code>send()</code> algorithm</span>.</p></li>
1408:
1409: <li><p>The user agent <em class="ct">should</em> cancel any network
1410: activity for which the object is responsible.</p></li>
1.252 avankest 1411:
1412: <li><p>If there are any <span title="task">tasks</span> from the object's
1413: <span><code>XMLHttpRequest</code> task source</span> in one of the
1414: <span>task queues</span>, then remove those tasks.</p></li>
1.203 avankest 1415:
1416: <li><p>Set the <span>response entity body</span> to null.</p></li>
1417:
1.252 avankest 1418: <li><p>Empty the list of <span>author request headers</span>.</p></li>
1419:
1.203 avankest 1420: <li><p>Set the <span>error flag</span> to true.</p></li>
1421:
1422: <li>
1.272 avankest 1423: <p>If the state is <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span>,
1424: <span title="dom-XMLHttpRequest-OPENED">OPENED</span> with the
1.203 avankest 1425: <span><code>send()</code> flag</span> being false, or
1.272 avankest 1426: <span title="dom-XMLHttpRequest-DONE">DONE</span> go to the next step.</p>
1.12 avankest 1427:
1.203 avankest 1428: <p>Otherwise run these substeps:</p>
1.58 avankest 1429:
1430: <ol>
1.272 avankest 1431: <li><p>Switch the state to <span title="dom-XMLHttpRequest-DONE">DONE</span>.</p></li>
1.170 avankest 1432:
1.203 avankest 1433: <li><p>Set the <span><code>send()</code> flag</span> to false.</p></li>
1.96 avankest 1434:
1.203 avankest 1435: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.248 avankest 1436:
1437:
1.58 avankest 1438: </ol>
1.250 avankest 1439:
1.248 avankest 1440:
1.250 avankest 1441: <p class="note">A future version of this specification will dispatch an
1.273 avankest 1442: <code title="event-xhr-abort">abort</code> event here.</p>
1.248 avankest 1443:
1.203 avankest 1444: </li>
1445:
1446: <li>
1.272 avankest 1447: <p>Switch the state to <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span>.</p>
1.203 avankest 1448:
1.273 avankest 1449: <p class="note">No <code title="event-xhr-readystatechange">readystatechange</code> event is dispatched.</p>
1.203 avankest 1450: </li>
1451: </ol>
1452:
1453:
1454:
1.205 avankest 1455: <h3 id="response">Response</h3>
1.203 avankest 1456:
1457: <h4>The <code title="">status</code> attribute</h4>
1458:
1.276 avankest 1459: <dl class="domintro">
1460: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-status">status</code></dt>
1461: <dd><p>Returns the HTTP status code.</p></dd>
1462: </dl>
1463:
1464: <p>The
1465: <dfn id="dom-xmlhttprequest-status" title="dom-XMLHttpRequest-status"><code>status</code></dfn>
1466: attribute <em class="ct">must</em> return the result of running these
1467: steps:</p>
1.226 avankest 1468:
1.222 avankest 1469: <ol>
1.272 avankest 1470: <li><p>If the state is <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> or
1471: <span title="dom-XMLHttpRequest-OPENED">OPENED</span> return 0 and terminate these
1.222 avankest 1472: steps.</p></li>
1473:
1.239 avankest 1474: <li><p>If the <span>error flag</span> is true return 0 and terminate
1475: these steps.</p></li>
1.222 avankest 1476:
1477: <li><p>Return the HTTP status code.</p></li>
1.248 avankest 1478: </ol>
1.203 avankest 1479:
1480:
1481: <h4>The <code title="">statusText</code> attribute</h4>
1482:
1.276 avankest 1483: <dl class="domintro">
1484: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-statusText">statusText</code></dt>
1485: <dd><p>Returns the HTTP status text.</p></dd>
1486: </dl>
1487:
1488: <p>The
1489: <dfn id="dom-xmlhttprequest-statustext" title="dom-XMLHttpRequest-statusText"><code>statusText</code></dfn>
1490: attribute <em class="ct">must</em> return the result of running these
1491: steps:</p>
1.222 avankest 1492:
1493: <ol>
1.272 avankest 1494: <li><p>If the state is <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> or
1495: <span title="dom-XMLHttpRequest-OPENED">OPENED</span> return the empty string and
1.239 avankest 1496: terminate these steps.</p></li>
1.222 avankest 1497:
1498: <li><p>If the <span>error flag</span> is true return the empty string and
1499: terminate these steps.</p></li>
1500:
1501: <li><p>Return the HTTP status text.</p></li>
1502: </ol>
1.203 avankest 1503:
1504:
1505: <h4>The <code title="">getResponseHeader()</code> method</h4>
1506:
1.278 avankest 1507: <dl class="domintro">
1508: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-getResponseHeader">getResponseHeader(<var title="">header</var>)</dt>
1509: <dd><p>Returns the header field value from the response of which the
1510: field name matches <var title="">header</var>, unless the field name is
1511: <code>Set-Cookie</code> or <code>Set-Cookie2</code>.</p></dd>
1512: </dl>
1513:
1.203 avankest 1514: <p>When the
1.278 avankest 1515: <dfn id="dom-xmlhttprequest-getresponseheader" title="dom-XMLHttpRequest-getResponseHeader"><code>getResponseHeader(<var title="">header</var>)</code></dfn>
1.217 avankest 1516: is invoked, the user agent <em class="ct">must</em> run these steps:</p>
1.203 avankest 1517:
1518: <ol>
1.272 avankest 1519: <li><p>If the state is <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> or
1520: <span title="dom-XMLHttpRequest-OPENED">OPENED</span> return null and terminate these
1.203 avankest 1521: steps.</p></li>
1522:
1.239 avankest 1523: <li><p>If the <span>error flag</span> is true return null
1.203 avankest 1524: and terminate these steps.</p></li>
1525:
1.256 avankest 1526: <li><p>If any code point in <var>header</var> is higher than
1527: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS return null and terminate
1528: these steps.</p></li>
1529:
1530: <li><p>Let <var>header</var> be the result of
1531: <span title="deflate a DOMString into an byte sequence">deflating</span>
1532: <var>header</var>.</p></li> <!-- This sounds lame, but it works. -->
1533:
1534: <li><p>If <var>header</var> is a case-insensitive match for
1535: <code>Set-Cookie</code> or <code>Set-Cookie2</code> return null and
1536: terminate these steps.</p></li>
1.203 avankest 1537:
1.256 avankest 1538: <li><p>If <var>header</var> is a case-insensitive match for multiple HTTP
1539: response headers, return the
1540: <span title="inflate an byte sequence into a DOMString">inflated</span>
1541: values of these headers as a single concatenated string separated from
1542: each other by a U+002C COMMA U+0020 SPACE character pair and terminate
1543: these steps.</p></li>
1.203 avankest 1544:
1.256 avankest 1545: <li><p>If <var>header</var> is a case-insensitive match for a single HTTP
1546: response header, return the
1547: <span title="inflate an byte sequence into a DOMString">inflated</span>
1548: value of that header and terminate these steps.</p></li>
1.203 avankest 1549:
1.239 avankest 1550: <li><p>Return null.</p></li>
1.203 avankest 1551: </ol>
1552:
1.248 avankest 1553:
1554:
1.203 avankest 1555: <div class="example">
1.250 avankest 1556:
1557: <p>For the following script:</p>
1558:
1559: <pre><code>var client = new XMLHttpRequest();
1560: client.open("GET", "unicorns-are-teh-awesome.txt", true);
1.5 avankest 1561: client.send();
1.12 avankest 1562: client.onreadystatechange = function() {
1.250 avankest 1563: if(this.readyState == 2) {
1564: print(client.getResponseHeader("Content-Type"));
1565: }
1566: }</code></pre>
1567:
1568: <p>The <code>print()</code> function will get to process something
1569: like:</p>
1.5 avankest 1570:
1.250 avankest 1571: <pre><code>text/plain; charset=UTF-8</code></pre>
1.203 avankest 1572: </div>
1.12 avankest 1573:
1574:
1.203 avankest 1575: <h4>The <code title="">getAllResponseHeaders()</code> method</h4>
1.14 avankest 1576:
1.278 avankest 1577: <dl class="domintro">
1578: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-getAllResponseHeaders">getAllResponseHeaders()</dt>
1579: <dd><p>Returns all headers from the response, with the exception of those
1580: whose field name is <code>Set-Cookie</code> or
1581: <code>Set-Cookie2</code>.</p></dd>
1582: </dl>
1583:
1.203 avankest 1584: <p>When the
1.270 avankest 1585: <dfn id="dom-xmlhttprequest-getallresponseheaders"><code>getAllResponseHeaders()</code></dfn>
1.203 avankest 1586: method is invoked, the user agent <em class="ct">must</em> run the
1587: following steps:</p>
1.58 avankest 1588:
1.203 avankest 1589: <ol>
1.272 avankest 1590: <li><p>If the state is <span title="dom-XMLHttpRequest-UNSENT">UNSENT</span> or
1591: <span title="dom-XMLHttpRequest-OPENED">OPENED</span> return the empty string and
1.239 avankest 1592: terminate these steps.</p></li>
1.203 avankest 1593:
1594: <li><p>If the <span>error flag</span> is true return the empty string and
1595: terminate these steps.</p></li>
1596:
1.256 avankest 1597: <li><p>Return all the HTTP headers, excluding headers that are a
1598: case-insensitive match for <code>Set-Cookie</code> or
1599: <code>Set-Cookie2</code>,
1600: <span title="inflate an byte sequence into a DOMString">inflated</span>,
1601: as a single string, with each header line
1602: separated by a U+000D CR U+000A LF pair, excluding the status line, and
1.203 avankest 1603: with each header name and header value separated by a
1604: U+003A COLON U+0020 SPACE pair.</p></li>
1605: </ol>
1.58 avankest 1606:
1.250 avankest 1607:
1608:
1.203 avankest 1609: <div class="example">
1.250 avankest 1610: <p>For the following script:</p>
1611:
1612: <pre><code>var client = new XMLHttpRequest();
1613: client.open("GET", "narwhals-too.txt", true);
1.5 avankest 1614: client.send();
1.12 avankest 1615: client.onreadystatechange = function() {
1.179 avankest 1616: if(this.readyState == 2) {
1.203 avankest 1617: print(this.getAllResponseHeaders());
1.12 avankest 1618: }
1.250 avankest 1619: }</code></pre>
1620:
1621: <p>The <code>print()</code> function will get to process something
1622: like:</p>
1.1 avankest 1623:
1.250 avankest 1624: <pre><code>Date: 2004年10月24日 04:58:38 GMT
1.203 avankest 1625: Server: Apache/1.3.31 (Unix)
1626: Keep-Alive: timeout=15, max=99
1627: Connection: Keep-Alive
1628: Transfer-Encoding: chunked
1629: Content-Type: text/plain; charset=utf-8</code></pre>
1630: </div>
1631:
1.250 avankest 1632:
1.203 avankest 1633:
1634: <h4>Response Entity Body</h4>
1635:
1.248 avankest 1636: <p>The <dfn id="response-mime-type">response MIME type</dfn> is the MIME
1637: type the <code>Content-Type</code> header contains without any
1638: parameters or null if the header could not be parsed properly or was
1639: omitted. The <dfn id="override-mime-type">override MIME type</dfn> is
1640: always null. <dfn id="final-mime-type">Final MIME type</dfn> is the
1641: override MIME type unless that is null in which case it is the response
1642: MIME type.</p>
1643:
1644: <p>The <dfn id="response-charset">response charset</dfn> is the value of
1645: the <code>charset</code> parameter of the <code>Content-Type</code> header
1646: or null if there was no <code>charset</code> parameter or if
1647: the header could not be parsed properly or was omitted. The
1648: <dfn id="override-charset">override charset</dfn> is always null.
1649: <dfn id="final-charset">Final charset</dfn> is the override charset unless
1650: that is null in which case it is the response charset.</p>
1.250 avankest 1651:
1.248 avankest 1652:
1653: <p class="note"><span>Override MIME type</span> and
1654: <span>override charset</span> are introduced here solely to make editing
1655: several levels of XMLHttpRequest simultaneously somewhat easier. Apologies
1656: for any confusion they might cause.</p>
1657:
1.250 avankest 1658:
1.248 avankest 1659: <hr>
1660:
1.203 avankest 1661: <p>The <dfn id="response-entity-body">response entity body</dfn> is the
1.255 avankest 1662: fragment of the <span>entity body</span> of the response received so far
1.272 avankest 1663: (<span title="dom-XMLHttpRequest-LOADING">LOADING</span>) or the complete entity body
1664: of the response (<span title="dom-XMLHttpRequest-DONE">DONE</span>). If the response
1.255 avankest 1665: does not have an entity body the response entity body is null.</p>
1666:
1667: <p class="note">The <span>response entity body</span> is updated as part
1.271 avankest 1668: of the <code title="dom-XMLHttpRequest-send">send()</code> algorithm.</p>
1.250 avankest 1669:
1.203 avankest 1670: <hr>
1671:
1672: <p>The <dfn id="text-response-entity-body">text response entity body</dfn>
1.248 avankest 1673: is a <code>DOMString</code> representing the <span>response entity
1674: body</span>. The text response entity body is the return value of the
1.203 avankest 1675: following algorithm:</p>
1676:
1677: <ol>
1.248 avankest 1678: <li><p>If the response entity body is null return the empty string and
1679: terminate these steps.</p>
1680:
1681: <li><p>Let <var>charset</var> be the <span>final charset</span>.</p></li>
1.203 avankest 1682:
1.248 avankest 1683: <li><p>Let <var>mime</var> be the <span>final MIME type</span>.</p></li>
1.203 avankest 1684:
1.248 avankest 1685: <li><p>If <var>charset</var> is null and <var>mime</var> is null,
1.203 avankest 1686: <code>text/xml</code>, <code>application/xml</code> or ends in
1.248 avankest 1687: <code title="">+xml</code> use the rules set forth in the XML
1688: specifications to determine the character encoding. Let
1689: <var>charset</var> be the determined character encoding.</p></li>
1690:
1691: <li><p>If <var>charset</var> is null and <var>mime</var> is
1692: <code>text/html</code> follow the rules set forth in the HTML
1693: specification to determine the character encoding. Let
1.203 avankest 1694: <var>charset</var> be the determined character encoding.
1695: [<cite><span>HTML5</span></cite>]</p></li>
1696:
1697: <li>
1698: <p>If <var>charset</var> is null then, for each of the rows in the
1699: following table, starting with the first one and going down, if the first
1700: bytes of <var>bytes</var> match the bytes given in the first column, then
1701: let <var>charset</var> be the encoding given in the cell in the second
1702: column of that row. If there is no match <var>charset</var> remains
1703: null.</p>
1704:
1705: <table>
1706: <thead>
1707: <tr>
1708: <th>Bytes in Hexadecimal
1709: <th>Description
1.237 avankest 1710: <tbody>
1.203 avankest 1711: <tr>
1712: <td>FE FF
1713: <td>UTF-16BE BOM
1714: <tr>
1715: <td>FF FE
1716: <td>UTF-16LE BOM
1717: <tr>
1718: <td>EF BB BF
1.237 avankest 1719: <td>UTF-8 BOM
1.203 avankest 1720: </table>
1721: </li>
1722:
1723: <li><p>If <var>charset</var> is null let <var>charset</var> be
1724: UTF-8.</p></li>
1725:
1726: <li><p>Return the result of decoding the response entity body using
1727: <var>charset</var>. Replace bytes or sequences of bytes that are not
1.248 avankest 1728: valid accordng to the <var>charset</var> with a single
1729: U+FFFD REPLACEMENT CHARACTER character.</p></li>
1.203 avankest 1730: </ol>
1731:
1732: <p class="note">Authors are strongly encouraged to encode their resources
1733: using UTF-8.</p>
1.248 avankest 1734:
1.203 avankest 1735: <hr>
1736:
1.248 avankest 1737: <p>The <dfn id="document-response-entity-body">document response entity
1738: body</dfn> is either a <code>Document</code> representing the
1739: <span>response entity body</span> or null. The document
1740: response entity body is the return value of the following algorithm:</p>
1.12 avankest 1741:
1.203 avankest 1742: <ol>
1743: <li><p>If the <span>response entity body</span> is null terminate these
1.239 avankest 1744: steps and return null.</p></li>
1.12 avankest 1745:
1.248 avankest 1746: <li><p>If <span>final MIME type</span> is not null,
1747: <code>text/xml</code>,
1748: <code>application/xml</code>, and does not end in
1749: <code title="">+xml</code> terminate these steps and return
1750: null.</li>
1751:
1752:
1.203 avankest 1753:
1754: <li>
1.265 avankest 1755: <p>Let <var>document</var> be a
1756: <span>cookie-free <code>Document</code> object</span> that represents
1757: the result of parsing the response entity body into a document tree
1758: following the rules from the XML specifications. If this fails
1759: (unsupported character encoding, namespace well-formedness error et
1760: cetera) terminate these steps return null.
1761: [<cite><span>XML</span></cite>]</p>
1.248 avankest 1762:
1763: <p class="note">Scripts in the resulting document tree will not be executed,
1764: resources referenced will not be loaded and no associated XSLT will be
1765: applied.</p>
1.203 avankest 1766: </li>
1.88 avankest 1767:
1.248 avankest 1768: <li><p>Return <var>document</var>.</p></li>
1.203 avankest 1769: </ol>
1.12 avankest 1770:
1771:
1.248 avankest 1772:
1773:
1774:
1.203 avankest 1775: <h4>The <code title="">responseText</code> attribute</h4>
1.12 avankest 1776:
1.276 avankest 1777: <dl class="domintro">
1778: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-responseText">responseText</code></dt>
1779: <dd><p>Returns the <span>text response entity body</span>.</p></dd>
1780: </dl>
1781:
1782: <p>The
1783: <dfn id="dom-xmlhttprequest-responsetext" title="dom-XMLHttpRequest-responseText"><code>responseText</code></dfn>
1784: attribute <em class="ct">must</em> return the result of running these
1785: steps:</p>
1.79 avankest 1786:
1.203 avankest 1787: <ol>
1.272 avankest 1788: <li><p>If the state is not <span title="dom-XMLHttpRequest-LOADING">LOADING</span> or
1789: <span title="dom-XMLHttpRequest-DONE">DONE</span> return the empty string and
1.203 avankest 1790: terminate these steps.</p></li>
1.75 avankest 1791:
1.203 avankest 1792: <li><p>Return the <span>text response entity body</span>.</p></li>
1793: </ol>
1.12 avankest 1794:
1795:
1.203 avankest 1796: <h4>The <code title="">responseXML</code> attribute</h4>
1.12 avankest 1797:
1.276 avankest 1798: <dl class="domintro">
1799: <dt><var title="">client</var> . <code title="dom-XMLHttpRequest-responseXML">responseXML</code></dt>
1800: <dd><p>Returns the <span>document response entity body</span>.</p></dd>
1801: </dl>
1802:
1803:
1804: <p>The
1805: <dfn id="dom-xmlhttprequest-responsexml" title="dom-XMLHttpRequest-responseXML"><code>responseXML</code></dfn>
1806: attribute <em class="ct">must</em> return the result of running these
1807: steps:</p>
1.12 avankest 1808:
1.203 avankest 1809: <ol>
1.272 avankest 1810: <li><p>If the state is not <span title="dom-XMLHttpRequest-DONE">DONE</span> return
1.239 avankest 1811: null and terminate these steps.</p></li>
1.12 avankest 1812:
1.248 avankest 1813: <li><p>Return the <span>document response entity body</span>.</p></li>
1.203 avankest 1814: </ol>
1.121 avankest 1815:
1.248 avankest 1816:
1817:
1.12 avankest 1818:
1.240 avankest 1819: <h2 id="exceptions">Exceptions</h2>
1.24 avankest 1820:
1.138 avankest 1821: <p>Several algorithms in this specification may result in an exception
1822: being thrown. These exceptions are all part of the group
1.185 avankest 1823: <code>ExceptionCode</code> and use the <code>DOMException</code> object,
1.138 avankest 1824: which is defined in DOM Level 3 Core. In addition this specification
1825: extends the <code>ExceptionCode</code> group with several new
1826: constants as indicated below. [<cite><span>DOM3Core</span></cite>]</p>
1.203 avankest 1827:
1.193 avankest 1828: <p class="note">Thus, exceptions used by this specification and not
1829: defined in this section are defined by DOM Level 3 Core.</p>
1.31 avankest 1830:
1.138 avankest 1831: <pre class="idl">const unsigned short <span>SECURITY_ERR</span> = 18;
1.199 avankest 1832: const unsigned short <span>NETWORK_ERR</span> = 19;
1833: const unsigned short <span>ABORT_ERR</span> = 20;</pre>
1.31 avankest 1834:
1.138 avankest 1835: <p>The <dfn id="security-err"><code>SECURITY_ERR</code></dfn> exception is
1836: raised if an attempt is made to perform an operation or access some data
1837: in a way that would be a security risk or a violation of the user agent's
1838: security policy.</p>
1839:
1840: <!-- http://lists.w3.org/Archives/Public/public-webapi/2006May/0027.html -->
1841:
1.33 avankest 1842: <p>The <dfn id="network-err"><code>NETWORK_ERR</code></dfn> exception is
1.138 avankest 1843: raised when a network error occurs in synchronous requests.</p>
1.121 avankest 1844:
1.138 avankest 1845: <p>The <dfn id="abort-err"><code>ABORT_ERR</code></dfn> exception is
1846: raised when the user aborts a request in synchronous requests.</p>
1.248 avankest 1847:
1848:
1.203 avankest 1849:
1.240 avankest 1850: <p class="note">These exceptions will be folded into an update of
1.199 avankest 1851: DOM Level 3 Core in due course, as they are appropriate for other API
1852: specifications as well.</p>
1.121 avankest 1853:
1.29 avankest 1854:
1.203 avankest 1855:
1.248 avankest 1856:
1857:
1.203 avankest 1858:
1.248 avankest 1859: <h2 class="no-num" id="references">References</h2>
1.203 avankest 1860:
1.177 avankest 1861: <p>Unless marked "Non-normative" these references are normative.</p>
1.11 avankest 1862:
1.6 avankest 1863: <dl>
1.230 avankest 1864: <dt>[<dfn id="ref-cookies">COOKIES</dfn>]</dt>
1.268 avankest 1865: <dd><cite><a href="http://tools.ietf.org/html/draft-ietf-httpstate-cookie">HTTP
1866: State Management Mechanism</a></cite> (work in progress), A. Barth. IETF.</dd>
1.203 avankest 1867:
1.248 avankest 1868:
1869:
1.155 avankest 1870: <dt>[<dfn id="ref-dom2events">DOM2Events</dfn>]</dt>
1871: <dd><cite><a href="http://www.w3.org/TR/DOM-Level-2-Events/">Document
1.267 avankest 1872: Object Model (DOM) Level 2 Events Specification</a></cite>, T. Pixley.
1873: W3C.</dd>
1.155 avankest 1874:
1.145 avankest 1875: <dt>[<dfn id="ref-dom3core">DOM3Core</dfn>]</dt>
1.11 avankest 1876: <dd><cite><a href="http://www.w3.org/TR/DOM-Level-3-Core">Document Object
1.92 avankest 1877: Model (DOM) Level 3 Core Specification</a></cite>, A. Le Hors, P. Le
1.267 avankest 1878: Hégaret, L. Wood, G. Nicol, J. Robie, M. Champion, S. Byrne.
1879: W3C.</dd>
1.11 avankest 1880:
1.117 avankest 1881: <dt>[<dfn id="ref-ecmascript">ECMAScript</dfn>]</dt>
1.92 avankest 1882: <dd><cite><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">ECMAScript
1.267 avankest 1883: Language Specification</a></cite>. ECMA.</dd>
1.248 avankest 1884:
1885:
1.171 avankest 1886:
1.145 avankest 1887: <dt>[<dfn id="ref-html5">HTML5</dfn>]</dt>
1.250 avankest 1888: <dd><cite><a href="http://www.w3.org/html/wg/html5/">HTML5</a></cite>
1.267 avankest 1889: (work in progress), I. Hickson. W3C.</dd>
1.250 avankest 1890: <dd><cite><a href="http://www.whatwg.org/specs/html5/current-work/">HTML5</a></cite>
1.267 avankest 1891: (work in progress), I. Hickson. WHATWG.</dd>
1.198 avankest 1892:
1893: <dt>[<dfn id="ref-httpverbsec">HTTPVERBSEC</dfn>]</dt>
1.248 avankest 1894: <dd>(Non-normative)
1895: <cite><a href="http://www.kb.cert.org/vuls/id/867593">Multiple vendors'
1896: web servers enable HTTP TRACE method by default</a></cite>, US-CERT.</dd>
1897: <dd>(Non-normative)
1898: <cite><a href="http://www.kb.cert.org/vuls/id/288308">Microsoft Internet
1899: Information Server (IIS) vulnerable to cross-site scripting via HTTP
1900: TRACK method</a></cite>, US-CERT.</dd>
1901: <dd>(Non-normative)
1902: <cite><a href="http://www.kb.cert.org/vuls/id/150227">HTTP proxy default
1903: configurations allow arbitrary TCP connections</a></cite>, US-CERT.</dd>
1904:
1905:
1906:
1907: <dt>[<dfn id="ref-rfc2046">RFC2046</dfn>]</dt>
1908: <dd><cite><a href="http://ietf.org/rfc/rfc2046">Multipurpose Internet Mail
1909: Extensions (MIME) Part Two: Media Types</a></cite>, N. Freed, N.
1.267 avankest 1910: Borenstein. IETF.</dd>
1.198 avankest 1911:
1.145 avankest 1912: <dt>[<dfn id="ref-rfc2119">RFC2119</dfn>]</dt>
1.117 avankest 1913: <dd><cite><a href="http://ietf.org/rfc/rfc2119">Key words for use in RFCs to
1.267 avankest 1914: Indicate Requirement Levels</a></cite>, S. Bradner. IETF.</dd>
1.12 avankest 1915:
1.248 avankest 1916: <dt>[<dfn id="rfc-rfc2616">RFC2616</dfn>]</dt>
1.11 avankest 1917: <dd><cite><a href="http://ietf.org/rfc/rfc2616">Hypertext Transfer Protocol
1.92 avankest 1918: -- HTTP/1.1</a></cite>, R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L.
1.267 avankest 1919: Masinter, P. Leach, T. Berners-Lee. IETF.</dd>
1.12 avankest 1920:
1.37 avankest 1921: <dt>[<dfn id="ref-rfc2617">RFC2617</dfn>]</dt>
1.11 avankest 1922: <dd><cite><a href="http://ietf.org/rfc/rfc2617">HTTP Authentication: Basic
1.92 avankest 1923: and Digest Access Authentication</a></cite>, P. Hallam-Baker, J.
1.267 avankest 1924: Hostetler, S. Lawrence, P. Leach, A. Luotonen, L. Stewart. IETF.</dd>
1.12 avankest 1925:
1.37 avankest 1926: <dt>[<dfn id="ref-rfc3986">RFC3986</dfn>]</dt>
1.11 avankest 1927: <dd><cite><a href="http://ietf.org/rfc/rfc3986">Uniform Resource Identifier
1.267 avankest 1928: (URI): Generic Syntax</a></cite>, T. Berners-Lee, R. Fielding, L.
1929: Masinter. IETF.</dd>
1.184 avankest 1930:
1.248 avankest 1931: <dt>[<dfn id=ref-rfc3987>RFC3987</dfn>]</dt>
1932: <dd><cite><a href="http://ietf.org/rfc/rfc3987">Internationalized
1.267 avankest 1933: Resource Identifiers (IRIs)</a></cite>, M. Duerst, M. Suignard.
1934: IETF.</dd>
1.248 avankest 1935:
1.203 avankest 1936: <dt>[<dfn id="ref-webidl">WebIDL</dfn>]</dt>
1.200 avankest 1937: <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web
1.267 avankest 1938: IDL</a></cite> (work in progress), C. McCormack. W3C.</dd> <!-- XXX add Sam -->
1.181 avankest 1939:
1.92 avankest 1940: <dt>[<dfn id="ref-xml">XML</dfn>]</dt>
1941: <dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup Language
1.267 avankest 1942: (XML) 1.0</a></cite>, T. Bray, J. Paoli, C. Sperberg-McQueen, E. Maler,
1943: F. Yergeau. W3C.</dd>
1944: <dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in
1945: XML</a></cite>, T. Bray, D. Hollander, A. Layman, R. Tobin, H. S.
1946: Thompson. W3C.</dd>
1.1 avankest 1947: </dl>
1.11 avankest 1948:
1.203 avankest 1949:
1950:
1.130 avankest 1951: <h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
1.11 avankest 1952:
1.159 avankest 1953: <p>The editor would like to thank
1.12 avankest 1954:
1.163 avankest 1955: Addison Phillips,
1.159 avankest 1956: Ahmed Kamel,
1957: Alex Hopmann,
1958: Alex Vincent,
1959: Alexey Proskuryakov,
1960: Asbjørn Ulsberg,
1961: Boris Zbarsky,
1962: Björn Höhrmann,
1963: Cameron McCormack,
1964: Christophe Jolif,
1965: Charles McCathieNevile,
1966: Dan Winship,
1.248 avankest 1967: David Andersson,
1.159 avankest 1968: David Håsäther,
1.248 avankest 1969: David Levin,
1.159 avankest 1970: Dean Jackson,
1971: Denis Sureau,
1972: Doug Schepers,
1973: Douglas Livingstone,
1974: Elliotte Harold,
1975: Eric Lawrence,
1.196 avankest 1976: Erik Dahlström,
1.163 avankest 1977: Geoffrey Sneddon,
1.159 avankest 1978: Gideon Cohn,
1979: Gorm Haug Eriksen,
1.247 avankest 1980: Håkon Wium Lie,
1.159 avankest 1981: Hallvord R. M. Steen,
1.247 avankest 1982: Huub Schaeks,
1.159 avankest 1983: Ian Davis,
1984: Ian Hickson,
1985: Ivan Herman,
1986: Jeff Walden,
1987: Jens Lindström,
1988: Jim Deegan,
1989: Jim Ley,
1990: Joe Farro,
1991: Jonas Sicking,
1992: Julian Reschke,
1993: Karl Dubost,
1.175 avankest 1994: Lachlan Hunt,
1.159 avankest 1995: Maciej Stachowiak,
1996: Magnus Kristiansen,
1997: Marc Hadley,
1998: Marcos Caceres,
1999: Mark Baker,
1.203 avankest 2000: Mark Birbeck,
1.159 avankest 2001: Mark Nottingham,
1.267 avankest 2002: Mark S. Miller,
1.248 avankest 2003: Martin Hassman,
1.159 avankest 2004: Mohamed Zergaoui,
1.256 avankest 2005: Olli Pettay,
1.159 avankest 2006: Pawel Glowacki,
1.231 avankest 2007: Peter Michaux,
1.264 avankest 2008: Philip Taylor,
1.159 avankest 2009: Robin Berjon,
1.248 avankest 2010: Rune Halvorsen,
1.159 avankest 2011: Ruud Steltenpool,
2012: Simon Pieters,
2013: Stewart Brodie,
2014: Sunava Dutta,
1.186 avankest 2015: Thomas Roessler,
1.203 avankest 2016: Tom Magliery, and
1.159 avankest 2017: Zhenbin Xu
1.181 avankest 2018:
1.159 avankest 2019: for their contributions to this specification.</p>
1.12 avankest 2020:
1.1 avankest 2021: <p>Special thanks to the Microsoft employees who first implemented the
1.143 avankest 2022: <code title="">XMLHttpRequest</code> interface, which was first widely
2023: deployed by the Windows Internet Explorer browser.</p>
1.12 avankest 2024:
1.143 avankest 2025: <p>Special thanks also to the WHATWG for drafting an initial version of
2026: this specification in their Web Applications 1.0 document (now renamed to
1.250 avankest 2027: HTML5). [<cite><span>HTML5</span></cite>]</p>
1.12 avankest 2028:
1.143 avankest 2029: <p>Thanks also to all those who have helped to improve this specification
2030: by sending suggestions and corrections. (Please, keep bugging us with your
1.22 avankest 2031: issues!)</p>
1.1 avankest 2032: </body>
2033: </html>
1.211 avankest 2034:
Webmaster