Annotation of 2006/webapi/XMLHttpRequest/Overview.src.html, revision 1.269
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.232 avankest 389: name <code>readystatechange</code>, which does not bubble and is not
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>
421: attribute <span>Function</span> <span>onreadystatechange</span>;
1.58 avankest 422:
1.205 avankest 423: // <a href="#states">states</a>
1.71 avankest 424: const unsigned short <span title="UNSENT state">UNSENT</span> = 0;
1.134 avankest 425: const unsigned short <span title="OPENED state">OPENED</span> = 1;
1.123 avankest 426: const unsigned short <span title="HEADERS_RECEIVED state">HEADERS_RECEIVED</span> = 2;
1.86 avankest 427: const unsigned short <span title="LOADING state">LOADING</span> = 3;
1.117 avankest 428: const unsigned short <span title="DONE state">DONE</span> = 4;
1.70 avankest 429: readonly attribute unsigned short <span>readyState</span>;
1.58 avankest 430:
1.205 avankest 431: // <a href="#request">request</a>
1.226 avankest 432: void <span>open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>);
433: void <span>open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>, boolean <var>async</var>);
1.228 avankest 434: void <span>open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>, boolean <var>async</var>, DOMString? <var>user</var>);
435: void <span>open</span>(DOMString <var>method</var>, DOMString <var title="">url</var>, boolean <var>async</var>, DOMString? <var>user</var>, DOMString? <var>password</var>);
1.226 avankest 436: void <span>setRequestHeader</span>(DOMString <var>header</var>, DOMString <var>value</var>);
1.70 avankest 437: void <span>send</span>();
1.226 avankest 438: void <span>send</span>(Document <var>data</var>);
1.228 avankest 439: void <span>send</span>([AllowAny] DOMString? <var>data</var>);
1.70 avankest 440: void <span>abort</span>();
1.58 avankest 441:
1.205 avankest 442: // <a href="#response">response</a>
1.203 avankest 443: readonly attribute unsigned short <span>status</span>;
444: readonly attribute DOMString <span>statusText</span>;
1.226 avankest 445: DOMString <span>getResponseHeader</span>(DOMString <var>header</var>);
1.70 avankest 446: DOMString <span>getAllResponseHeaders</span>();
447: readonly attribute DOMString <span>responseText</span>;
448: readonly attribute Document <span>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.203 avankest 492: <p>When the
1.266 avankest 493: <dfn id="dom-xmlhttprequest" title="dom-XMLHttpRequest"><code>XMLHttpRequest()</code></dfn>
1.203 avankest 494: constructor is invoked, the user agent <em class="ct">must</em> return a
495: new <code>XMLHttpRequest</code> object.</p>
496:
1.263 avankest 497:
1.203 avankest 498:
1.205 avankest 499: <h3 id="event-handler-attributes">Event Handler Attributes</h3>
500:
1.248 avankest 501:
502:
1.205 avankest 503: <p>The following is the
504: <span title="event handler attributes">event handler attribute</span> (and
505: its corresponding <span>event handler event type</span>) that
506: <em class="ct">must</em> be supported as DOM attribute by the
507: <code>XMLHttpRequest</code> object:</p>
508:
509: <table>
510: <thead>
511: <tr>
512: <th><span title="event handler attributes">event handler attribute</span>
513: <th><span>event handler event type</span>
514: <tbody>
515: <tr>
516: <td><dfn id="onreadystatechange"><code>onreadystatechange</code></dfn>
517: <td><code>readystatechange</code></td>
518: </table>
519:
520:
521: <h3 id="states">States</h3>
1.203 avankest 522:
523: <p>The <code>XMLHttpRequest</code> object can be in several states. The
524: <dfn id="readystate"><code>readyState</code></dfn> attribute, on getting,
525: <em class="ct">must</em> return the current state, which
526: <em class="ct">must</em> be one of the following values:</p>
527:
528: <dl>
529: <dt><dfn id="unsent-state" title="UNSENT state"><code>UNSENT</code></dfn>
530: (numeric value 0)</dt>
531: <dd><p>The object has been constructed.</p></dd>
532:
533: <dt><dfn id="opened-state" title="OPENED state"><code>OPENED</code></dfn>
534: (numeric value 1)</dt>
535: <dd><p>The <code>open()</code> method has been successfully invoked.
536: During this state request headers can be set using
537: <code>setRequestHeader()</code> and the request can be made using the
538: <code>send()</code> method.</p></dd>
539:
540: <dt><dfn id="headers-received-state" title="HEADERS_RECEIVED state"><code>HEADERS_RECEIVED</code></dfn>
541: (numeric value 2)</dt>
1.257 avankest 542: <dd><p>All redirects (if any) have been followed and all HTTP headers of
543: the final response have been received. Several response members of the
544: object are now available.</p></dd>
1.203 avankest 545:
546: <dt><dfn id="loading-state" title="LOADING state"><code>LOADING</code></dfn>
547: (numeric value 3)</dt>
548: <dd><p>The <span>response entity body</span> is being received.</p></dd>
549:
550: <dt><dfn id="done-state" title="DONE state"><code>DONE</code></dfn>
551: (numeric value 4)</dt>
552: <dd><p>The data transfer has been completed or something went wrong
553: during the transfer (e.g. infinite redirects).</p></dd>
554: </dl>
555:
556: <p>The <span title="OPENED state">OPENED</span> state has an associated
557: <dfn id="send-flag"><code>send()</code> flag</dfn> that indicates whether
558: the <code>send()</code> method has been invoked. It can be either true
559: or false and has an initial value of false.</p>
560:
561: <p>The <span title="DONE state">DONE</span> state has an associated
562: <dfn id="error-flag">error flag</dfn> that indicates some type of network
563: error or abortion. It can be either true or false and has an initial value
564: of false.</p>
565:
566:
1.205 avankest 567: <h3 id="request">Request</h3>
1.203 avankest 568:
569: <p>The <code>XMLHttpRequest</code> object holds the following request
570: metadata variables:</p>
571:
1.204 avankest 572: <dl>
573: <dt>The <dfn>asynchronous flag</dfn></dt>
1.266 avankest 574: <dd>True when <span title="fetch">fetching</span> is done asychronously.
575: False when fetching is done synchronously.</dd>
1.204 avankest 576:
577: <dt>The <dfn>request method</dfn></dt>
578: <dd>The method used in the request.</dd>
579:
580: <dt>The <dfn>request URL</dfn></dt>
581: <dd>The <span>URL</span> used in the request.</dd>
1.218 avankest 582:
1.204 avankest 583: <dt>The <dfn>request username</dfn></dt>
584: <dd>The username used in the request or null if there is no
585: username.</dd>
1.218 avankest 586:
1.204 avankest 587: <dt>The <dfn>request password</dfn></dt>
588: <dd>The password used in the request or null if there is no
589: password.</dd>
1.218 avankest 590:
1.204 avankest 591: <dt>The <dfn id="author-request-headers">author request headers</dfn></dt>
592: <dd>A list consisting of HTTP header name/value pairs to be used in the
593: request.</p>
1.203 avankest 594:
1.204 avankest 595: <dt>The <dfn>request entity body</dfn></dt>
1.218 avankest 596: <dd>The <span>entity body</span> used in the request.</dd>
1.248 avankest 597:
598:
1.204 avankest 599: </dl>
1.203 avankest 600:
1.248 avankest 601:
602:
1.203 avankest 603:
604: <h4>The <code title="">open()</code> method</h4>
1.269 ! avankest 605:
! 606: <dl class="domintro">
! 607: <dt><var title="">client</var> . <code title="open">open(<var>method</var>,
! 608: <var title="">url</var>, <var>async</var>, <var>user</var>,
! 609: <var>password</var>)</code></dt>
! 610:
! 611: <dd><p>Sets the <span>request method</span>, <span>request URL</span>,
! 612: <span>asynchronous flag</span>, <span>request username</span>, and
! 613: <span>request password</span>.</p></dd>
! 614: </dl>
1.88 avankest 615:
1.203 avankest 616: <p>When the <dfn id="open" title="open"><code>open(<var>method</var>,
617: <var title="">url</var>, <var>async</var>, <var>user</var>,
618: <var>password</var>)</code></dfn> method is invoked, the user agent
1.217 avankest 619: <em class="ct">must</em> run these steps (unless otherwise indicated):</p>
1.90 avankest 620:
1.88 avankest 621: <ol>
1.203 avankest 622: <li>
623: <p>If the <code>XMLHttpRequest</code> object has an associated
624: <span><code>XMLHttpRequest</code> <code>Document</code></span> run
625: these substeps:</p>
1.90 avankest 626:
1.203 avankest 627: <ol>
628: <li><p>If the
629: <span><code>XMLHttpRequest</code> <code>Document</code></span> is not
630: <span>fully active</span> raise an <code>INVALID_STATE_ERR</code>
631: exception and terminate the overall set of steps.</p></li>
632:
633: <li><p>Let <span><code>XMLHttpRequest</code> base URL</span> be the
634: <span>document base URL</span> of the
635: <span><code>XMLHttpRequest</code> <code>Document</code></span>.</p></li>
636:
637: <li><p>Let <span><code>XMLHttpRequest</code> origin</span> be the
638: <span>origin</span> of the
639: <span><code>XMLHttpRequest</code> <code>Document</code></span>.</p></li>
640: </ol>
641: </li>
1.90 avankest 642:
1.256 avankest 643: <li><p>If any code point in <var>method</var> is higher than
644: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS or after
645: <span title="deflate a DOMString into an byte sequence">deflating</span>
646: <var>method</var> it does not match the
1.210 avankest 647: <span>Method token</span> production raise a <code>SYNTAX_ERR</code>
1.256 avankest 648: exception and terminate these steps. Otherwise let <var>method</var> be
649: the result of
650: <span title="deflate a DOMString into an byte sequence">deflating</span>
651: <var>method</var>.</p></li> <!-- This sounds lame, but it works. -->
1.118 avankest 652:
1.115 avankest 653: <li>
1.256 avankest 654: <p>If <var>method</var> is a case-insensitive match for
1.203 avankest 655: <code>CONNECT</code>, <code>DELETE</code>, <code>GET</code>,
656: <code>HEAD</code>, <code>OPTIONS</code>, <code>POST</code>,
657: <code>PUT</code>, <code>TRACE</code>, or <code>TRACK</code>
1.256 avankest 658: subtract 0x20 from each byte in the range 0x61 (ASCII a) to
659: 0x7A (ASCII z).</p>
1.118 avankest 660:
1.203 avankest 661: <p class="note">If it does not match any of the above, it is passed
662: through <em>literally</em>, including in the final request.</p>
1.115 avankest 663: </li>
1.203 avankest 664: <!-- WebKit (and supposedly Gecko) also uppercase: COPY, INDEX, LOCK,
665: M-POST, MKCOL, MOVE, PROPFIND, PROPPATCH, and UNLOCK. -->
1.118 avankest 666:
1.111 avankest 667: <li>
1.256 avankest 668: <p>If <var>method</var> is a case-sensitive match for
1.259 avankest 669: <code>CONNECT</code>, <code>TRACE</code>, or <code>TRACK</code> raise a
670: <code>SECURITY_ERR</code> exception and terminate these steps.</p>
1.117 avankest 671:
1.203 avankest 672: <p class="note">Allowing these methods poses a security risk.
673: [<cite><span>HTTPVERBSEC</span></cite>]</p>
1.111 avankest 674: </li>
675:
1.203 avankest 676: <li><p>Let <var title="">url</var> be a <span>URL</span>.</p></li>
677:
1.209 avankest 678: <li><p>Let <span>URL character encoding</span> of <var title="">url</var>
679: be UTF-8.</p></li>
1.113 avankest 680:
1.255 avankest 681: <li><p><span title="Resolve a URL">Resolve</span> <var title="">url</var>
1.203 avankest 682: relative to the <span><code>XMLHttpRequest</code> base URL</span>.
683: If the algorithm returns an error raise a <code>SYNTAX_ERR</code>
684: exception and terminate these steps.</p></li>
685:
686: <!-- Presto and Gecko override the encoding. WebKit does not. Trident
687: does not support non-ASCII URLs. This matters for the <query> component,
688: see HTML5. -->
689:
690: <li><p>Drop <code><fragment></code> from <var title="">url</var>.</p></li>
691:
692: <li><p>If <var title="">url</var> contains an unsupported <code><scheme></code>
693: raise a <code>NOT_SUPPORTED_ERR</code> and terminate these
694: steps.</p></li>
695:
696: <li><p>If the <code>"user:password"</code> format in the
697: <code>userinfo</code> production is not supported for the relevant scheme
698: and <var title="">url</var> contains this format raise a
699: <code>SYNTAX_ERR</code> and terminate these steps.</p></li>
700:
701: <li><p>If <var title="">url</var> contains the <code>"user:password"</code>
702: format let <var>temp user</var> be the user part and
703: <var>temp password</var> be the password part.</p></li>
704:
705: <li><p>If <var title="">url</var> just contains the <code>"user"</code>
706: format let <var>temp user</var> be the user part.</p></li>
707:
1.248 avankest 708:
1.203 avankest 709: <li><p>If the <span>origin</span> of <var title="">url</var> is not
710: <span>same origin</span> with the
1.259 avankest 711: <span><code>XMLHttpRequest</code> origin</span> raise a
712: <code>SECURITY_ERR</code> exception and terminate these steps.</p></li>
1.248 avankest 713:
714:
1.203 avankest 715:
1.211 avankest 716: <li><p>Let <var>async</var> be the value of the <var>async</var> argument
1.266 avankest 717: or true if it was omitted.</p></li>
1.203 avankest 718:
719: <li>
720: <p>If the <var>user</var> argument was not omitted follow these sub
721: steps:</p>
1.90 avankest 722:
1.203 avankest 723: <ol>
1.263 avankest 724:
725:
1.203 avankest 726: <li><p>If the syntax of <var>user</var> does not match the syntax
727: specified by the relevant authentication scheme, raise a
728: <code>SYNTAX_ERR</code> exception and terminate the overall set of
729: steps.</p></li>
1.163 avankest 730:
1.239 avankest 731: <li><p>If <var>user</var> is null let <var>temp user</var>
1.203 avankest 732: be null.</p></li>
1.90 avankest 733:
1.203 avankest 734: <li><p>Otherwise let <var>temp user</var> be <var>user</var>.</p></li>
735: </ol>
1.88 avankest 736:
1.203 avankest 737: <p class="note">These steps override anything that may have been set by
738: the <var title="">url</var> argument.</p>
739: </li>
1.88 avankest 740:
1.128 avankest 741: <li>
1.203 avankest 742: <p>If the <var>password</var> argument was not omitted follow these sub
743: steps:</p>
744:
745: <ol>
1.263 avankest 746:
747:
1.203 avankest 748: <li><p>If the syntax of <var>password</var> does not match the syntax
749: specified by the relevant authentication scheme, raise a
750: <code>SYNTAX_ERR</code> exception and terminate the overall set of
751: steps.</p></li>
1.167 avankest 752:
1.239 avankest 753: <li><p>If <var>password</var> is null let
1.203 avankest 754: <var>temp password</var> be null.</p></li>
755:
756: <li><p>Otherwise let <var>temp password</var> be
757: <var>password</var>.</p></li>
758: </ol>
759:
760: <p class="note">These steps override anything that may have been set by
761: the <var title="">url</var> argument.</p>
1.128 avankest 762: </li>
1.88 avankest 763:
1.203 avankest 764: <li><p><span title="abort send()">Abort the <code>send()</code> algorithm</span>.</p></li>
765:
766: <li><p>The user agent <em class="ct">should</em> cancel any network
767: activity for which the object is responsible.</p></li>
768: <!-- we can hardly require it... -->
769:
1.252 avankest 770: <li><p>If there are any <span title="task">tasks</span> from the object's
771: <span><code>XMLHttpRequest</code> task source</span> in one of the
772: <span>task queues</span>, then remove those tasks.</p></li>
773:
1.203 avankest 774: <li>
775: <p>Set variables associated with the object as follows:</p>
776:
777: <ul>
778: <li><p>Set the <span><code>send()</code> flag</span> to false.</p></li>
779:
780: <li><p>Set <span>response entity body</span> to null.</p></li>
781:
782: <li><p>Empty the list of <span>author request headers</span>.</p>
783:
784: <li><p>Set the <span>request method</span> to <var>method</var>.</p></li>
785:
786: <li><p>Set the <span>request URL</span> to <var title="">url</var>.</p></li>
1.58 avankest 787:
1.203 avankest 788: <li><p>Set the <span>request username</span> to <var>temp user</var>.</p></li>
1.12 avankest 789:
1.203 avankest 790: <li><p>Set the <span>request password</span> to <var>temp password</var>.</p></li>
1.12 avankest 791:
1.266 avankest 792: <li><p>Set the <span>asynchronous flag</span> to the value of
793: <var>async</var>.</p></li>
1.203 avankest 794: </ul>
795: </li>
1.58 avankest 796:
1.203 avankest 797: <li><p>Switch the the state to
798: <span title="OPENED state">OPENED</span>.</p></li>
1.58 avankest 799:
1.203 avankest 800: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
801: </ol>
1.248 avankest 802:
803:
1.203 avankest 804: <p class="note">A future version or extension of this specification will
805: define a way of doing cross-origin requests.</p>
1.248 avankest 806:
1.58 avankest 807:
1.14 avankest 808:
1.203 avankest 809: <h4>The <code title="">setRequestHeader()</code> method</h4>
1.12 avankest 810:
1.235 avankest 811: <!-- XXX domintro authors
1.203 avankest 812: The <code>setRequestHeader()</code> method can be used to set new request
1.184 avankest 813: headers and append to request headers already in the list.</p>
1.203 avankest 814: -->
1.45 avankest 815:
1.203 avankest 816: <p>As indicated in the algorithm below certain headers cannot be set and
817: are left up to the user agent. In addition there are certain other headers
818: the user agent will take control of if they are not set by the author as
819: indicated at the end of the <code>send()</code> method section.</p>
820:
821: <p class="note">The <code>setRequestHeader()</code> method appends a
822: value if the HTTP header given as argument is already part of the
823: <span>author request headers</span> list.</p>
824:
1.248 avankest 825:
826:
1.203 avankest 827: <p>When the
828: <dfn id="setrequestheader" title="setrequestheader"><code>setRequestHeader(<var>header</var>,
829: <var>value</var>)</code></dfn> method is invoked, the user agent
1.259 avankest 830: <em class="ct">must</em> run these steps:</p>
1.14 avankest 831:
1.203 avankest 832: <ol>
833: <li><p>If the state is not <span title="OPENED state">OPENED</span> raise
834: an <code>INVALID_STATE_ERR</code> exception and terminate these
835: steps.</p></li>
836:
837: <li><p>If the <span><code>send()</code> flag</span> is true raise an
838: <code>INVALID_STATE_ERR</code> exception and terminate these
839: steps.</p></li>
840:
1.256 avankest 841: <li><p>If any code point in <var>header</var> is higher than
842: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS or after
843: <span title="deflate a DOMString into an byte sequence">deflating</span>
844: <var>header</var> it does not match the
845: <span>field-name</span> production raise a <code>SYNTAX_ERR</code>
846: exception and terminate these steps. Otherwise let <var>header</var> be
847: the result of
848: <span title="deflate a DOMString into an byte sequence">deflating</span>
849: <var>header</var>.</p></li> <!-- This sounds lame, but it works. -->
1.203 avankest 850:
851: <li>
1.256 avankest 852: <p>If any code point in <var>value</var> is higher than
853: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS or after
854: <span title="deflate a DOMString into an byte sequence">deflating</span>
855: <var>value</var> it does not match the
856: <span>field-value</span> production raise a <code>SYNTAX_ERR</code>
857: exception and terminate these steps. Otherwise let <var>value</var> be
858: the result of
859: <span title="deflate a DOMString into an byte sequence">deflating</span>
860: <var>value</var>.</p> <!-- This sounds lame, but it works. -->
1.203 avankest 861:
862: <p class="note">The empty string is legal and represents the empty
863: header value.</p>
864: </li>
865:
866: <li>
1.259 avankest 867: <p>Terminate these steps if <var>header</var> is a case-insensitive
868: match for one of the following headers:</p>
1.203 avankest 869:
870: <ul>
871: <li><code>Accept-Charset</code></li>
872: <li><code>Accept-Encoding</code></li>
873: <li><code>Connection</code></li>
874: <li><code>Content-Length</code></li>
875: <li><code>Cookie</code></li>
876: <li><code>Cookie2</code></li>
877: <li><code>Content-Transfer-Encoding</code></li>
878: <li><code>Date</code></li>
879: <li><code>Expect</code></li>
880: <li><code>Host</code></li>
881: <li><code>Keep-Alive</code></li>
882: <li><code>Referer</code></li>
883: <li><code>TE</code></li>
884: <li><code>Trailer</code></li>
885: <li><code>Transfer-Encoding</code></li>
886: <li><code>Upgrade</code></li>
887: <li><code>User-Agent</code></li>
888: <li><code>Via</code></li>
889: </ul>
1.96 avankest 890:
1.256 avankest 891: <p>… or if the start of <var>header</var> is a case-insensitive
892: match for <code>Proxy-</code> or <code>Sec-</code> (including when
893: <var>header</var> is just <code>Proxy-</code> or <code>Sec-</code>).</p>
1.203 avankest 894:
895: <p class="note">The above headers are not allowed to be set as they are
896: better controlled by the user agent as it knows best what value they
1.259 avankest 897: ought to have. Header names starting with <code>Sec-</code> are not
1.203 avankest 898: allowed to be set to allow new headers to be minted in the future that
899: are guaranteed not to come from <code>XMLHttpRequest</code>. (Older
900: clients would however still be vulnerable as they allow such headers to
901: be set.)</p>
902: </li>
1.14 avankest 903:
1.203 avankest 904: <li><p>If <var>header</var> is not in the
905: <span>author request headers</span> list append <var>header</var> with
906: its associated <var>value</var> to the list and terminate these
907: steps.</p></li>
908:
909: <li><p>If <var>header</var> is in the <span>author request headers</span>
910: list either use multiple headers, combine the values or use a combination
911: of those (section 4.2, RFC 2616).
912: [<cite><span>RFC2616</span></cite>]</p></li>
913: <!-- XXX it seems UAs always combine the values -->
914: </ol>
1.45 avankest 915:
1.203 avankest 916: <p class="note">See also the <code>send()</code> method regarding user
917: agent header handling for caching, authentication, proxies, and
918: cookies.</p>
1.14 avankest 919:
1.203 avankest 920: <div class="example">
921: <pre><code>// The following script:
1.14 avankest 922: var client = new XMLHttpRequest();
923: client.open('GET', 'demo.cgi');
924: client.setRequestHeader('X-Test', 'one');
925: client.setRequestHeader('X-Test', 'two');
926: client.send();
927:
928: // ...would result in the following header being sent:
929: ...
930: X-Test: one, two
1.58 avankest 931: ...</code></pre>
1.203 avankest 932: </div>
1.255 avankest 933:
1.248 avankest 934:
1.218 avankest 935:
1.203 avankest 936:
937: <h4>The <code title="">send()</code> method</h4>
1.12 avankest 938:
1.235 avankest 939: <!-- XXX domintro
1.203 avankest 940: <p>The <code>send()</code> method initiates the request and its optional
1.204 avankest 941: argument provides the <span>request entity body</span>.</p>
1.235 avankest 942: -->
1.203 avankest 943:
944: <p>When the
945: <dfn id="send" title="send"><code>send(<var>data</var>)</code></dfn>
946: method is invoked, the user agent <em class="ct">must</em> run the
947: following steps (unless otherwise noted). This algorithm gets aborted when
948: the <code>open()</code> or <code>abort()</code> method is invoked. When
949: the
950: <dfn title="abort send()" id="abort-send-algorithm"><code>send()</code> algorithm is aborted</dfn>
951: the user agent <em class="ct">must</em> terminate the algorithm after
952: finishing the step it is on.</p>
953:
954: <p class="note">The <code title="">send()</code> algorithm can only be
955: aborted when the <span>asynchronous flag</span> is true and only after the
956: method call has returned.</p>
1.181 avankest 957:
1.203 avankest 958: <ol>
959: <li><p>If the state is not <span title="OPENED state">OPENED</span> raise
960: an <code>INVALID_STATE_ERR</code> exception and terminate these
961: steps.</p></li>
962:
963: <li><p>If the <span><code>send()</code> flag</span> is true raise an
964: <code>INVALID_STATE_ERR</code> exception and terminate these
965: steps.</p></li>
1.58 avankest 966:
1.203 avankest 967: <li>
968: <p>If the <span>request method</var> is <code>GET</code> or
1.239 avankest 969: <code>HEAD</code> act as if <var>data</var> is null.</p>
1.232 avankest 970:
971: <p>If the <var>data</var> argument has been omitted or is
1.239 avankest 972: null, do not include a <span>request entity body</span>
1.232 avankest 973: and go to the next step.</p>
1.248 avankest 974:
975: <p>Otherwise, let <var>encoding</var> be null, <var>mime type</var> be
976: null, and then follow these rules:</p>
1.203 avankest 977:
978: <dl class="switch">
1.248 avankest 979:
980:
981: <dt>If <var>data</var> is a <code>Document</code>
1.203 avankest 982:
983: <dd>
1.232 avankest 984: <p>Let <var>encoding</var> be the <span>preferred MIME name</span> of
985: the
986: <span title="document's character encoding">character encoding</span>
987: of <var>data</var>. If <var>encoding</var> is UTF-16 change it to
988: UTF-8.</p>
989:
1.248 avankest 990: <p>Let <var>mime type</var> be "<code>application/xml;charset=</code>"
991: followed by <var>encoding</var>.</p>
1.232 avankest 992:
993: <p>Let the <span>request entity body</span> be the result of getting
994: the <code title="dom-innerHTML">innerHTML</code> attribute on
1.233 avankest 995: <var>data</var>
996: <span title="convert a DOMString to a sequence of Unicode characters">converted to Unicode</span>
997: and encoded as <var>encoding</var>. Re-raise any exception this
998: raises.</p>
1.218 avankest 999:
1.233 avankest 1000: <p class="note">In particular, if the document cannot be serialized an
1.217 avankest 1001: <code>INVALID_STATE_ERR</code> exception is raised.</p>
1002:
1.203 avankest 1003: <p class="note">Subsequent changes to the <code>Document</code> have
1004: no effect on what is submitted.</p>
1005: </dd>
1.237 avankest 1006:
1.248 avankest 1007: <dt>If <var>data</var> is a <code>DOMString</code></dt>
1.237 avankest 1008:
1.248 avankest 1009: <dd>
1010: <p>Let <var>encoding</var> be UTF-8.</p>
1011:
1012: <p>Let <var>mime type</var> be "<code>text/plain;charset=UTF-8</code>".</p>
1013:
1014: <p>Let the <span>request entity body</span> be <var>data</var>
1015: <span title="convert a DOMString to a sequence of Unicode characters">converted to Unicode</span>
1016: and encoded as UTF-8.</p>
1017: </dd>
1018:
1019:
1.203 avankest 1020: </dl>
1.58 avankest 1021:
1.232 avankest 1022: <p>If a <code>Content-Type</code> header is set using
1.248 avankest 1023: <code>setRequestHeader()</code> whose value is a
1024: <span>valid MIME type</span> and has a <code>charset</code>
1.256 avankest 1025: parameter whose value is not a case-insensitive match for
1026: <var>encoding</var>, and <var>encoding</var> is not null, set all the
1027: <code>charset</code> parameters of the <code>Content-Type</code> header
1028: to <var>encoding</var>.</p>
1.232 avankest 1029:
1030: <p>If no <code>Content-Type</code> header has been set using
1.248 avankest 1031: <code>setRequestHeader()</code> and <var>mime type</var> is not null set
1032: a <code>Content-Type</code> request header with as value
1033: <var>mime type</var>.</p>
1.236 avankest 1034:
1035: <!-- reminder: if we ever change this to always include charset it has
1036: to be included as the first parameter for compatibility reasons -->
1.203 avankest 1037: </li>
1.202 avankest 1038:
1.203 avankest 1039: <li><p>If the <span>asynchronous flag</span> is false release the
1040: <span>storage mutex</span>.</p></li>
1.103 avankest 1041:
1.248 avankest 1042:
1043:
1.203 avankest 1044: <li><p>Set the <span>error flag</span> to false.</p></li>
1.218 avankest 1045:
1.248 avankest 1046:
1047:
1.211 avankest 1048: <li>
1049: <p>If the <span>asynchronous flag</span> is true run these substeps:</p>
1.218 avankest 1050:
1.211 avankest 1051: <ol>
1.217 avankest 1052: <li><p>Set the <span><code>send()</code> flag</span> to true.</p></li>
1053:
1.211 avankest 1054: <li>
1055: <p><span>Dispatch a <code>readystatechange</code> event</span>.</p>
1.145 avankest 1056:
1.211 avankest 1057: <p class="note">The state does not change. The event is dispatched for
1058: historical reasons.</p>
1059: </li>
1060:
1.248 avankest 1061:
1062:
1.211 avankest 1063: <li><p>Return the <code>send()</code> method call, but continue running
1064: the steps in this algorithm.</p></li>
1065: </ol>
1066: </li>
1.218 avankest 1067:
1.203 avankest 1068: <li>
1.248 avankest 1069:
1.211 avankest 1070:
1.261 avankest 1071: <p><span>Fetch</span> the <span>request URL</span> from
1.260 avankest 1072: <i title="">origin</i>
1073: <span><code>XMLHttpRequest</code> origin</span>, with the
1074: <i title="">synchronous flag</i> set if the
1075: <span>asynchronous flag</span> is false, using HTTP method
1.248 avankest 1076: <span>request method</span>, user <span>request username</span> (if
1077: non-null) and password <span>request password</span> (if non-null),
1078: taking into account the <span>request entity body</span>, list of
1079: <span>author request headers</span> and the rules listed at the end of
1080: this section.</p>
1081:
1082: <dl class="switch">
1083: <dt>If the <span>asynchronous flag</span> is false</dt>
1084: <dd>
1085: <p>While making the request also follow the
1086: <span>same-origin request event rules</span>.</p>
1087:
1088: <!--
1089: This cannot involve any task queue whatsoever because that would
1090: mean other tasks on the task queue might get processed as well
1091: which is counter to the whole idea of doing things synchronous.
1092: -->
1093:
1094: <p class="note">The <code>send()</code> method call will now be
1095: returned by virtue of this algorithm ending.</p>
1096: </dd>
1097:
1098: <dt>If the <span>asynchronous flag</span> is true</dt>
1099: <dd>
1100: <p><span>Make progress notifications</span>.</p>
1101:
1102: <p><span>Make upload progress notifications</span>.</p>
1103:
1104: <p>While processing the request, as data becomes available and when
1105: the user interferes with the request,
1.255 avankest 1106: <span title="queue a task">queue tasks</span> to update the
1107: <span>response entity body</span> and follow the
1.254 avankest 1108: <span>same-origin request event rules</span>.</p>
1.248 avankest 1109: </dd>
1110: </dl>
1111:
1.203 avankest 1112: </li>
1113: </ol>
1.60 avankest 1114:
1.203 avankest 1115: <hr>
1116:
1.227 avankest 1117: <p>If the user agent allows the end user to configure a proxy it
1.248 avankest 1118: <em class="ct">should</em> modify the request appropriately; i.e., connect
1119: to the proxy host instead of the origin server, modify the
1120: <code>Request-Line</code> and send <code>Proxy-Authorization</code>
1121: headers as specified.</p>
1.262 avankest 1122:
1123: <hr>
1.212 avankest 1124:
1.218 avankest 1125: <p>If the user agent supports HTTP Authentication and
1.262 avankest 1126: <code title="http-authorization">Authorization</code> is not in the list
1127: of <span>author request headers</span>, it <em class="ct">should</em>
1.218 avankest 1128: consider requests originating from the <code>XMLHttpRequest</code> object
1129: to be part of the protection space that includes the accessed URIs and
1.262 avankest 1130: send <code title="http-authorization">Authorization</code> headers and
1131: handle <code>401 Unauthorized</code> requests appropriately.</p>
1132:
1133: <p>If authentication fails,
1134: <code title="http-authorization">Authorization</code> is not in the list
1135: of <span>author request headers</span>, <span>request username</span> is
1136: null, and <span>request password</span> is null, user agents
1137: <em class="ct">should</em> prompt the end user for their username and
1138: password.</p>
1139:
1140: <p>If authentication fails,
1141: <code title="http-authorization">Authorization</code> is not in the list
1142: of <span>author request headers</span>, <span>request username</span> is
1143: non-null, and <span>request password</span> is non-null, user agents
1144: <em class="ct">must not</em> prompt the end user for their username and
1145: password. [<cite><span>RFC2617</span></cite>]</p>
1.212 avankest 1146:
1.266 avankest 1147: <p class="note">End users are not prompted if username/password are
1148: provided through the <code>open()</code> API so that authors can implement
1149: their own user interface.</p>
1.262 avankest 1150:
1151: <hr>
1.212 avankest 1152:
1153: <p>If the user agent supports HTTP State Management it
1154: <em class="ct">should</em> persist, discard and send cookies (as received
1155: in the <code>Set-Cookie</code> and <code>Set-Cookie2</code> response
1156: headers, and sent in the <code>Cookie</code> header) as applicable.
1157: [<cite><span>COOKIES</span></cite>]</p>
1.262 avankest 1158:
1159: <hr>
1.212 avankest 1160:
1161: <p>If the user agent implements a HTTP cache it <em class="ct">should</em>
1.248 avankest 1162: respect <code>Cache-Control</code> request headers set by the
1163: <code>setRequestHeader()</code> (e.g., <code>Cache-Control:
1164: no-cache</code> bypasses the cache). It <em class="ct">must not</em> send
1.212 avankest 1165: <code>Cache-Control</code> or <code>Pragma</code> request headers
1.227 avankest 1166: automatically unless the end user explicitly requests such behavior
1.212 avankest 1167: (e.g. by (force-)reloading the page).</p>
1168:
1169: <p>For <code>304 Not Modified</code> responses that are a result of a
1170: user agent generated conditional request the user agent
1171: <em class="ct">must</em> act as if the server gave a <code>200 OK</code>
1172: response with the appropriate content. The user agent
1173: <em class="ct">must</em> allow <code>setRequestHeader()</code> to
1.248 avankest 1174: override automatic cache validation by setting request headers (e.g.
1175: <code>If-None-Match</code> or <code>If-Modified-Since</code>), in which
1.212 avankest 1176: case <code>304 Not Modified</code> responses <em class="ct">must</em> be
1177: passed through. [<cite><span>RFC2616</span></cite>]</p>
1.262 avankest 1178:
1179: <hr>
1.212 avankest 1180:
1181: <p>If the user agent implements server-driven content-negotiation
1182: it <em class="ct">should</em> set <code>Accept-Encoding</code> and
1.231 avankest 1183: <code>Accept-Charset</code> headers as appropriate. For
1184: <code>Accept</code> and <code>Accept-Language</code> the user agent
1185: <em class="ct">must</em> follow these constraints:</p>
1186:
1187: <ul>
1188: <li><p>Both headers <em class="ct">must not</em> be modified if they are
1189: already set through <code>setRequestHeader()</code>.</p></li>
1.255 avankest 1190:
1.231 avankest 1191: <li><p>If not set through <code>setRequestHeader()</code>
1.255 avankest 1192: <code>Accept-Language</code> <em class="ct">should</em> be set as
1.231 avankest 1193: appropriate.</p></li>
1194:
1195: <li><p>If not set through <code>setRequestHeader()</code>
1196: <code>Accept</code> <em class="ct">must</em> be set with as value
1197: <code>*/*</code>.</p></li>
1198: </ul>
1199:
1200: <p>Responses <em class="ct">must</em> have the content-encodings
1201: automatically decoded. [<cite><span>RFC2616</span></cite>]</p>
1.212 avankest 1202:
1.262 avankest 1203: <hr>
1204:
1.212 avankest 1205: <p>Besides the <span>author request headers</span> user agents
1206: <em class="ct">should not</em> include additional request headers other
1.248 avankest 1207: than those mentioned above or other than those authors are not allowed to
1208: set using <code>setRequestHeader()</code>. This ensures that authors have
1209: a reasonably predictable API.</p>
1.218 avankest 1210:
1.212 avankest 1211:
1212: <h4>Infrastructure for the <code title="">send()</code> method</h4>
1.216 avankest 1213:
1.219 avankest 1214: <p>The <dfn>same-origin request event rules</dfn> are as follows:</p>
1.118 avankest 1215:
1.203 avankest 1216: <dl class="switch">
1217: <dt>If the response is an HTTP redirect</dt>
1218: <dd>
1.248 avankest 1219:
1.257 avankest 1220: <p>If the <span>origin</span> of the <span>URL</span> conveyed by the
1221: <code title="http-location">Location</code> header is
1222: <span>same origin</span> with the
1223: <span><code>XMLHttpRequest</code> origin</span> and the redirect does
1224: not violate infinite loop precautions, transparently follow the redirect
1225: while observing the <span>same-origin request event rules</span>.</p>
1.248 avankest 1226:
1227: <p>Otherwise, this is a <span>network error</span>.</p>
1228:
1229:
1.203 avankest 1230:
1231: <p class="note">HTTP places requirements on the user agent regarding the
1.204 avankest 1232: preservation of the <span>request method</span> and
1.248 avankest 1233: <span>request entity body</span> during redirects, and also requires end
1234: users to be notified of certain kinds of automatic redirections.</p>
1.203 avankest 1235: <!-- XXX HTTP needs fixing here -->
1.213 avankest 1236: </dd>
1.121 avankest 1237:
1.227 avankest 1238: <dt>If the end user cancels the download</dt>
1.213 avankest 1239: <dd><p>This is an <span>abort error</span>.</p></dd>
1.60 avankest 1240:
1.214 avankest 1241: <dt>In case of network errors</dt>
1.213 avankest 1242: <dd>
1243: <p>In case of DNS errors, TLS negotiation failure, or other type of
1244: network errors, this is a <span>network error</span>. Do not request any
1.227 avankest 1245: kind of end user interaction.</p>
1.121 avankest 1246:
1.213 avankest 1247: <p class="note">This does not include HTTP responses that indicate
1248: some type of error, such as HTTP status code 410.</p>
1249: </dd>
1.60 avankest 1250:
1.248 avankest 1251:
1252:
1.213 avankest 1253: <dt>Once all HTTP headers have been received and the
1.257 avankest 1254: <span>asynchronous flag</span> is true (and this is not an HTTP
1255: redirect)</dt>
1.213 avankest 1256: <dd><p><span>Switch to the HEADERS_RECEIVED state</span>.</p></dd>
1.186 avankest 1257:
1.220 avankest 1258: <dt>Once the first byte (or more) of the
1259: <span>response entity body</span> has been received and the
1260: <span>asynchronous flag</span> is true</dt>
1261: <dt>If there is no <span>response entity body</span> and the
1.213 avankest 1262: <span>asynchronous flag</span> is true</dt>
1.215 avankest 1263: <dd><p><span>Switch to the LOADING state</span>.</p></dd>
1.220 avankest 1264:
1265: <dt>Once the whole <span>response entity body</span> has been
1266: received</dt>
1.224 avankest 1267: <dt>If there is no <span>response entity body</span> and the
1268: <span>asynchronous flag</span> is false or the state is
1.221 avankest 1269: <span title="LOADING state">LOADING</span></dt>
1.220 avankest 1270: <dd><p><span>Switch to the DONE state</span>.</p></dd>
1.213 avankest 1271: </dl>
1.218 avankest 1272:
1.248 avankest 1273:
1274:
1.213 avankest 1275: <hr>
1.218 avankest 1276:
1.241 avankest 1277: <p>When something is said to be a <dfn>network error</dfn> run the
1278: <span>request error</span> steps for exception
1279: <code>NETWORK_ERR</code>.</p>
1280:
1281: <p>When something is said to be an <dfn>abort error</dfn> run the
1282: <span>request error</span> steps for exception
1283: <code>ABORT_ERR</code>.</p>
1.60 avankest 1284:
1.248 avankest 1285:
1286:
1.242 avankest 1287: <p>When something is said to be a <dfn>request error</dfn> for
1.248 avankest 1288: exception <var>exception</var> run these
1289: steps:</p>
1.12 avankest 1290:
1.213 avankest 1291: <ol>
1.254 avankest 1292: <li><p>The user agent <em class="ct">should</em> cancel any network
1293: activity for which the object is responsible.</p></li>
1294:
1295: <li><p>If there are any <span title="task">tasks</span> from the object's
1296: <span><code>XMLHttpRequest</code> task source</span> in one of the
1297: <span>task queues</span>, then remove those tasks.</p></li>
1.250 avankest 1298:
1.213 avankest 1299: <li><p>Set the <span>response entity body</span> to null.</p></li>
1.203 avankest 1300:
1.254 avankest 1301: <li><p>Empty the list of <span>author request headers</span>.</p></li>
1302:
1.213 avankest 1303: <li><p>Set the the <span>error flag</span> to true.</p></li>
1.12 avankest 1304:
1.213 avankest 1305: <li><p>Switch the state to <span title="DONE state">DONE</span>.</p></li>
1.203 avankest 1306:
1.241 avankest 1307: <li><p>If the <span>asynchronous flag</span> is false raise an
1308: <var>exception</var> exception and terminate the overall set of
1.213 avankest 1309: steps.</p></li>
1.203 avankest 1310:
1.248 avankest 1311: <li>
1.249 avankest 1312: <p><span>Dispatch a <code>readystatechange</code> event</span>.</p>
1.248 avankest 1313:
1314: <p class="note">At this point it is clear that the
1315: <span>asynchronous flag</span> is true.</p>
1316: </li>
1317:
1318:
1.203 avankest 1319:
1.248 avankest 1320: <li><p>Terminate the overall algorithm.</p></li>
1.213 avankest 1321: </ol>
1.203 avankest 1322:
1.248 avankest 1323:
1324: <p class="note">A future version of this specification will dispatch an
1325: <code>error</code>/<code>abort</code> event here as well. (Depending on
1326: the type of error.)</p>
1327:
1.203 avankest 1328:
1.213 avankest 1329: <hr>
1.203 avankest 1330:
1.213 avankest 1331: <p>When it is said to
1332: <dfn id="switch-headers-received">switch to the HEADERS_RECEIVED state</dfn>
1333: run these steps:</p>
1.203 avankest 1334:
1.213 avankest 1335: <ol>
1336: <li><p>Switch the state to <span title="HEADERS_RECEIVED state">HEADERS_RECEIVED</span>.</p></li>
1.203 avankest 1337:
1.249 avankest 1338: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.213 avankest 1339: </ol>
1.218 avankest 1340:
1.213 avankest 1341: <p>When it is said to
1342: <dfn id="switch-loading">switch to the LOADING state</dfn> run these
1343: steps:</p>
1.218 avankest 1344:
1.213 avankest 1345: <ol>
1346: <li><p>Switch the state to <span title="LOADING state">LOADING</span>.</p></li>
1.203 avankest 1347:
1.249 avankest 1348: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.213 avankest 1349: </ol>
1.218 avankest 1350:
1.216 avankest 1351: <p>When it is said to
1352: <dfn id="switch-done">switch to the DONE state</dfn> run these steps:</p>
1.218 avankest 1353:
1.216 avankest 1354: <ol>
1.255 avankest 1355: <li><p>If the <span>asynchronous flag</span> is false update the
1356: <span>response entity body</span>.</p></li>
1357:
1.216 avankest 1358: <li><p>Switch the state to <span title="DONE state">DONE</span>.</p></li>
1359:
1.248 avankest 1360: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1361:
1.220 avankest 1362:
1.216 avankest 1363: </ol>
1.218 avankest 1364:
1.248 avankest 1365:
1366:
1.203 avankest 1367:
1368: <h4>The <code title="">abort()</code> method</h4>
1369:
1370: <p>When the <dfn id="abort"><code>abort()</code></dfn> method is invoked,
1.217 avankest 1371: the user agent <em class="ct">must</em> run these steps (unless otherwise
1372: noted):</p>
1.12 avankest 1373:
1.203 avankest 1374: <ol>
1375: <li><p><span title="abort send()">Abort the <code>send()</code> algorithm</span>.</p></li>
1376:
1377: <li><p>The user agent <em class="ct">should</em> cancel any network
1378: activity for which the object is responsible.</p></li>
1.252 avankest 1379:
1380: <li><p>If there are any <span title="task">tasks</span> from the object's
1381: <span><code>XMLHttpRequest</code> task source</span> in one of the
1382: <span>task queues</span>, then remove those tasks.</p></li>
1.203 avankest 1383:
1384: <li><p>Set the <span>response entity body</span> to null.</p></li>
1385:
1.252 avankest 1386: <li><p>Empty the list of <span>author request headers</span>.</p></li>
1387:
1.203 avankest 1388: <li><p>Set the <span>error flag</span> to true.</p></li>
1389:
1390: <li>
1391: <p>If the state is <span title="UNSENT state">UNSENT</span>,
1392: <span title="OPENED state">OPENED</span> with the
1393: <span><code>send()</code> flag</span> being false, or
1394: <span title="DONE state">DONE</span> go to the next step.</p>
1.12 avankest 1395:
1.203 avankest 1396: <p>Otherwise run these substeps:</p>
1.58 avankest 1397:
1398: <ol>
1.203 avankest 1399: <li><p>Switch the state to <span title="DONE state">DONE</span>.</p></li>
1.170 avankest 1400:
1.203 avankest 1401: <li><p>Set the <span><code>send()</code> flag</span> to false.</p></li>
1.96 avankest 1402:
1.203 avankest 1403: <li><p><span>Dispatch a <code>readystatechange</code> event</span>.</p></li>
1.248 avankest 1404:
1405:
1.58 avankest 1406: </ol>
1.250 avankest 1407:
1.248 avankest 1408:
1.250 avankest 1409: <p class="note">A future version of this specification will dispatch an
1410: <code title="abort-event">abort</code> event here.</p>
1.248 avankest 1411:
1.203 avankest 1412: </li>
1413:
1414: <li>
1415: <p>Switch the state to <span title="UNSENT state">UNSENT</span>.</p>
1416:
1417: <p class="note">No <code>readystatechange</code> event is dispatched.</p>
1418: </li>
1419: </ol>
1420:
1421:
1422:
1.205 avankest 1423: <h3 id="response">Response</h3>
1.203 avankest 1424:
1425: <h4>The <code title="">status</code> attribute</h4>
1426:
1427: <p>The <dfn id="status"><code>status</code></dfn> attribute
1.222 avankest 1428: <em class="ct">must</em> return the result of running these steps:</p>
1.226 avankest 1429:
1.222 avankest 1430: <ol>
1431: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1432: <span title="OPENED state">OPENED</span> return 0 and terminate these
1.222 avankest 1433: steps.</p></li>
1434:
1.239 avankest 1435: <li><p>If the <span>error flag</span> is true return 0 and terminate
1436: these steps.</p></li>
1.222 avankest 1437:
1438: <li><p>Return the HTTP status code.</p></li>
1.248 avankest 1439: </ol>
1.203 avankest 1440:
1441:
1442: <h4>The <code title="">statusText</code> attribute</h4>
1443:
1444: <p>The <dfn id="statustext"><code>statusText</code></dfn> attribute
1.222 avankest 1445: <em class="ct">must</em> return the result of running these steps:</p>
1446:
1447: <ol>
1448: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1449: <span title="OPENED state">OPENED</span> return the empty string and
1450: terminate these steps.</p></li>
1.222 avankest 1451:
1452: <li><p>If the <span>error flag</span> is true return the empty string and
1453: terminate these steps.</p></li>
1454:
1455: <li><p>Return the HTTP status text.</p></li>
1456: </ol>
1.203 avankest 1457:
1458:
1459: <h4>The <code title="">getResponseHeader()</code> method</h4>
1460:
1461: <p>When the
1462: <dfn id="getresponseheader" title="getresponseheader"><code>getResponseHeader(<var>header</var>)</code></dfn>
1.217 avankest 1463: is invoked, the user agent <em class="ct">must</em> run these steps:</p>
1.203 avankest 1464:
1465: <ol>
1466: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1467: <span title="OPENED state">OPENED</span> return null and terminate these
1.203 avankest 1468: steps.</p></li>
1469:
1.239 avankest 1470: <li><p>If the <span>error flag</span> is true return null
1.203 avankest 1471: and terminate these steps.</p></li>
1472:
1.256 avankest 1473: <li><p>If any code point in <var>header</var> is higher than
1474: U+00FF LATIN SMALL LETTER Y WITH DIAERESIS return null and terminate
1475: these steps.</p></li>
1476:
1477: <li><p>Let <var>header</var> be the result of
1478: <span title="deflate a DOMString into an byte sequence">deflating</span>
1479: <var>header</var>.</p></li> <!-- This sounds lame, but it works. -->
1480:
1481: <li><p>If <var>header</var> is a case-insensitive match for
1482: <code>Set-Cookie</code> or <code>Set-Cookie2</code> return null and
1483: terminate these steps.</p></li>
1.203 avankest 1484:
1.256 avankest 1485: <li><p>If <var>header</var> is a case-insensitive match for multiple HTTP
1486: response headers, return the
1487: <span title="inflate an byte sequence into a DOMString">inflated</span>
1488: values of these headers as a single concatenated string separated from
1489: each other by a U+002C COMMA U+0020 SPACE character pair and terminate
1490: these steps.</p></li>
1.203 avankest 1491:
1.256 avankest 1492: <li><p>If <var>header</var> is a case-insensitive match for a single HTTP
1493: response header, return the
1494: <span title="inflate an byte sequence into a DOMString">inflated</span>
1495: value of that header and terminate these steps.</p></li>
1.203 avankest 1496:
1.239 avankest 1497: <li><p>Return null.</p></li>
1.203 avankest 1498: </ol>
1499:
1.248 avankest 1500:
1501:
1.203 avankest 1502: <div class="example">
1.250 avankest 1503:
1504: <p>For the following script:</p>
1505:
1506: <pre><code>var client = new XMLHttpRequest();
1507: client.open("GET", "unicorns-are-teh-awesome.txt", true);
1.5 avankest 1508: client.send();
1.12 avankest 1509: client.onreadystatechange = function() {
1.250 avankest 1510: if(this.readyState == 2) {
1511: print(client.getResponseHeader("Content-Type"));
1512: }
1513: }</code></pre>
1514:
1515: <p>The <code>print()</code> function will get to process something
1516: like:</p>
1.5 avankest 1517:
1.250 avankest 1518: <pre><code>text/plain; charset=UTF-8</code></pre>
1.203 avankest 1519: </div>
1.12 avankest 1520:
1521:
1.203 avankest 1522: <h4>The <code title="">getAllResponseHeaders()</code> method</h4>
1.14 avankest 1523:
1.203 avankest 1524: <p>When the
1525: <dfn id="getallresponseheaders"><code>getAllResponseHeaders()</code></dfn>
1526: method is invoked, the user agent <em class="ct">must</em> run the
1527: following steps:</p>
1.58 avankest 1528:
1.203 avankest 1529: <ol>
1530: <li><p>If the state is <span title="UNSENT state">UNSENT</span> or
1.239 avankest 1531: <span title="OPENED state">OPENED</span> return the empty string and
1532: terminate these steps.</p></li>
1.203 avankest 1533:
1534: <li><p>If the <span>error flag</span> is true return the empty string and
1535: terminate these steps.</p></li>
1536:
1.256 avankest 1537: <li><p>Return all the HTTP headers, excluding headers that are a
1538: case-insensitive match for <code>Set-Cookie</code> or
1539: <code>Set-Cookie2</code>,
1540: <span title="inflate an byte sequence into a DOMString">inflated</span>,
1541: as a single string, with each header line
1542: separated by a U+000D CR U+000A LF pair, excluding the status line, and
1.203 avankest 1543: with each header name and header value separated by a
1544: U+003A COLON U+0020 SPACE pair.</p></li>
1545: </ol>
1.58 avankest 1546:
1.250 avankest 1547:
1548:
1.203 avankest 1549: <div class="example">
1.250 avankest 1550: <p>For the following script:</p>
1551:
1552: <pre><code>var client = new XMLHttpRequest();
1553: client.open("GET", "narwhals-too.txt", true);
1.5 avankest 1554: client.send();
1.12 avankest 1555: client.onreadystatechange = function() {
1.179 avankest 1556: if(this.readyState == 2) {
1.203 avankest 1557: print(this.getAllResponseHeaders());
1.12 avankest 1558: }
1.250 avankest 1559: }</code></pre>
1560:
1561: <p>The <code>print()</code> function will get to process something
1562: like:</p>
1.1 avankest 1563:
1.250 avankest 1564: <pre><code>Date: 2004年10月24日 04:58:38 GMT
1.203 avankest 1565: Server: Apache/1.3.31 (Unix)
1566: Keep-Alive: timeout=15, max=99
1567: Connection: Keep-Alive
1568: Transfer-Encoding: chunked
1569: Content-Type: text/plain; charset=utf-8</code></pre>
1570: </div>
1571:
1.250 avankest 1572:
1.203 avankest 1573:
1574: <h4>Response Entity Body</h4>
1575:
1.248 avankest 1576: <p>The <dfn id="response-mime-type">response MIME type</dfn> is the MIME
1577: type the <code>Content-Type</code> header contains without any
1578: parameters or null if the header could not be parsed properly or was
1579: omitted. The <dfn id="override-mime-type">override MIME type</dfn> is
1580: always null. <dfn id="final-mime-type">Final MIME type</dfn> is the
1581: override MIME type unless that is null in which case it is the response
1582: MIME type.</p>
1583:
1584: <p>The <dfn id="response-charset">response charset</dfn> is the value of
1585: the <code>charset</code> parameter of the <code>Content-Type</code> header
1586: or null if there was no <code>charset</code> parameter or if
1587: the header could not be parsed properly or was omitted. The
1588: <dfn id="override-charset">override charset</dfn> is always null.
1589: <dfn id="final-charset">Final charset</dfn> is the override charset unless
1590: that is null in which case it is the response charset.</p>
1.250 avankest 1591:
1.248 avankest 1592:
1593: <p class="note"><span>Override MIME type</span> and
1594: <span>override charset</span> are introduced here solely to make editing
1595: several levels of XMLHttpRequest simultaneously somewhat easier. Apologies
1596: for any confusion they might cause.</p>
1597:
1.250 avankest 1598:
1.248 avankest 1599: <hr>
1600:
1.203 avankest 1601: <p>The <dfn id="response-entity-body">response entity body</dfn> is the
1.255 avankest 1602: fragment of the <span>entity body</span> of the response received so far
1603: (<span title="LOADING state">LOADING</span>) or the complete entity body
1604: of the response (<span title="DONE state">DONE</span>). If the response
1605: does not have an entity body the response entity body is null.</p>
1606:
1607: <p class="note">The <span>response entity body</span> is updated as part
1608: of the <code>send()</code> algorithm.</p>
1.250 avankest 1609:
1.203 avankest 1610: <hr>
1611:
1612: <p>The <dfn id="text-response-entity-body">text response entity body</dfn>
1.248 avankest 1613: is a <code>DOMString</code> representing the <span>response entity
1614: body</span>. The text response entity body is the return value of the
1.203 avankest 1615: following algorithm:</p>
1616:
1617: <ol>
1.248 avankest 1618: <li><p>If the response entity body is null return the empty string and
1619: terminate these steps.</p>
1620:
1621: <li><p>Let <var>charset</var> be the <span>final charset</span>.</p></li>
1.203 avankest 1622:
1.248 avankest 1623: <li><p>Let <var>mime</var> be the <span>final MIME type</span>.</p></li>
1.203 avankest 1624:
1.248 avankest 1625: <li><p>If <var>charset</var> is null and <var>mime</var> is null,
1.203 avankest 1626: <code>text/xml</code>, <code>application/xml</code> or ends in
1.248 avankest 1627: <code title="">+xml</code> use the rules set forth in the XML
1628: specifications to determine the character encoding. Let
1629: <var>charset</var> be the determined character encoding.</p></li>
1630:
1631: <li><p>If <var>charset</var> is null and <var>mime</var> is
1632: <code>text/html</code> follow the rules set forth in the HTML
1633: specification to determine the character encoding. Let
1.203 avankest 1634: <var>charset</var> be the determined character encoding.
1635: [<cite><span>HTML5</span></cite>]</p></li>
1636:
1637: <li>
1638: <p>If <var>charset</var> is null then, for each of the rows in the
1639: following table, starting with the first one and going down, if the first
1640: bytes of <var>bytes</var> match the bytes given in the first column, then
1641: let <var>charset</var> be the encoding given in the cell in the second
1642: column of that row. If there is no match <var>charset</var> remains
1643: null.</p>
1644:
1645: <table>
1646: <thead>
1647: <tr>
1648: <th>Bytes in Hexadecimal
1649: <th>Description
1.237 avankest 1650: <tbody>
1.203 avankest 1651: <tr>
1652: <td>FE FF
1653: <td>UTF-16BE BOM
1654: <tr>
1655: <td>FF FE
1656: <td>UTF-16LE BOM
1657: <tr>
1658: <td>EF BB BF
1.237 avankest 1659: <td>UTF-8 BOM
1.203 avankest 1660: </table>
1661: </li>
1662:
1663: <li><p>If <var>charset</var> is null let <var>charset</var> be
1664: UTF-8.</p></li>
1665:
1666: <li><p>Return the result of decoding the response entity body using
1667: <var>charset</var>. Replace bytes or sequences of bytes that are not
1.248 avankest 1668: valid accordng to the <var>charset</var> with a single
1669: U+FFFD REPLACEMENT CHARACTER character.</p></li>
1.203 avankest 1670: </ol>
1671:
1672: <p class="note">Authors are strongly encouraged to encode their resources
1673: using UTF-8.</p>
1.248 avankest 1674:
1.203 avankest 1675: <hr>
1676:
1.248 avankest 1677: <p>The <dfn id="document-response-entity-body">document response entity
1678: body</dfn> is either a <code>Document</code> representing the
1679: <span>response entity body</span> or null. The document
1680: response entity body is the return value of the following algorithm:</p>
1.12 avankest 1681:
1.203 avankest 1682: <ol>
1683: <li><p>If the <span>response entity body</span> is null terminate these
1.239 avankest 1684: steps and return null.</p></li>
1.12 avankest 1685:
1.248 avankest 1686: <li><p>If <span>final MIME type</span> is not null,
1687: <code>text/xml</code>,
1688: <code>application/xml</code>, and does not end in
1689: <code title="">+xml</code> terminate these steps and return
1690: null.</li>
1691:
1692:
1.203 avankest 1693:
1694: <li>
1.265 avankest 1695: <p>Let <var>document</var> be a
1696: <span>cookie-free <code>Document</code> object</span> that represents
1697: the result of parsing the response entity body into a document tree
1698: following the rules from the XML specifications. If this fails
1699: (unsupported character encoding, namespace well-formedness error et
1700: cetera) terminate these steps return null.
1701: [<cite><span>XML</span></cite>]</p>
1.248 avankest 1702:
1703: <p class="note">Scripts in the resulting document tree will not be executed,
1704: resources referenced will not be loaded and no associated XSLT will be
1705: applied.</p>
1.203 avankest 1706: </li>
1.88 avankest 1707:
1.248 avankest 1708: <li><p>Return <var>document</var>.</p></li>
1.203 avankest 1709: </ol>
1.12 avankest 1710:
1711:
1.248 avankest 1712:
1713:
1714:
1.203 avankest 1715: <h4>The <code title="">responseText</code> attribute</h4>
1.12 avankest 1716:
1.203 avankest 1717: <p>The <dfn id="responsetext"><code>responseText</code></dfn> attribute
1.217 avankest 1718: <em class="ct">must</em> return the result of running these steps:</p>
1.79 avankest 1719:
1.203 avankest 1720: <ol>
1.248 avankest 1721: <li><p>If the state is not <span title="LOADING state">LOADING</span> or
1722: <span title="DONE state">DONE</span> return the empty string and
1.203 avankest 1723: terminate these steps.</p></li>
1.75 avankest 1724:
1.203 avankest 1725: <li><p>Return the <span>text response entity body</span>.</p></li>
1726: </ol>
1.12 avankest 1727:
1728:
1.203 avankest 1729: <h4>The <code title="">responseXML</code> attribute</h4>
1.12 avankest 1730:
1.203 avankest 1731: <p>The <dfn id="responsexml"><code>responseXML</code></dfn> attribute
1.217 avankest 1732: <em class="ct">must</em> return the result of running these steps:</p>
1.12 avankest 1733:
1.203 avankest 1734: <ol>
1735: <li><p>If the state is not <span title="DONE state">DONE</span> return
1.239 avankest 1736: null and terminate these steps.</p></li>
1.12 avankest 1737:
1.248 avankest 1738: <li><p>Return the <span>document response entity body</span>.</p></li>
1.203 avankest 1739: </ol>
1.121 avankest 1740:
1.248 avankest 1741:
1742:
1.12 avankest 1743:
1.240 avankest 1744: <h2 id="exceptions">Exceptions</h2>
1.24 avankest 1745:
1.138 avankest 1746: <p>Several algorithms in this specification may result in an exception
1747: being thrown. These exceptions are all part of the group
1.185 avankest 1748: <code>ExceptionCode</code> and use the <code>DOMException</code> object,
1.138 avankest 1749: which is defined in DOM Level 3 Core. In addition this specification
1750: extends the <code>ExceptionCode</code> group with several new
1751: constants as indicated below. [<cite><span>DOM3Core</span></cite>]</p>
1.203 avankest 1752:
1.193 avankest 1753: <p class="note">Thus, exceptions used by this specification and not
1754: defined in this section are defined by DOM Level 3 Core.</p>
1.31 avankest 1755:
1.138 avankest 1756: <pre class="idl">const unsigned short <span>SECURITY_ERR</span> = 18;
1.199 avankest 1757: const unsigned short <span>NETWORK_ERR</span> = 19;
1758: const unsigned short <span>ABORT_ERR</span> = 20;</pre>
1.31 avankest 1759:
1.138 avankest 1760: <p>The <dfn id="security-err"><code>SECURITY_ERR</code></dfn> exception is
1761: raised if an attempt is made to perform an operation or access some data
1762: in a way that would be a security risk or a violation of the user agent's
1763: security policy.</p>
1764:
1765: <!-- http://lists.w3.org/Archives/Public/public-webapi/2006May/0027.html -->
1766:
1.33 avankest 1767: <p>The <dfn id="network-err"><code>NETWORK_ERR</code></dfn> exception is
1.138 avankest 1768: raised when a network error occurs in synchronous requests.</p>
1.121 avankest 1769:
1.138 avankest 1770: <p>The <dfn id="abort-err"><code>ABORT_ERR</code></dfn> exception is
1771: raised when the user aborts a request in synchronous requests.</p>
1.248 avankest 1772:
1773:
1.203 avankest 1774:
1.240 avankest 1775: <p class="note">These exceptions will be folded into an update of
1.199 avankest 1776: DOM Level 3 Core in due course, as they are appropriate for other API
1777: specifications as well.</p>
1.121 avankest 1778:
1.248 avankest 1779:
1.29 avankest 1780: <h2 class="no-num" id="notcovered">Not in this Specification</h2>
1781:
1.143 avankest 1782: <p><em>This section is non-normative.</em></p>
1.29 avankest 1783:
1.72 avankest 1784: <p>This specification does not include the following features which are
1785: being considered for a future version of this specification:</p>
1.29 avankest 1786:
1787: <ul>
1788: <li><code>load</code> event and <code>onload</code> attribute;</li>
1789: <li><code>error</code> event and <code>onerror</code> attribute;</li>
1790: <li><code>progress</code> event and <code>onprogress</code> attribute;</li>
1791: <li><code title="">abort</code> event and <code>onabort</code> attribute;</li>
1792: <li>Timers have been suggested, perhaps an <code>ontimeout</code>
1793: attribute;</li>
1794: <li>Property to disable following redirects;</li>
1.30 avankest 1795: <li><code title="">responseXML</code> for <code>text/html</code>
1796: documents;</li>
1.203 avankest 1797: <li>Cross-origin <code title="">XMLHttpRequest</code>;</li>
1.87 avankest 1798: <li><code>responseBody</code> to deal with byte streams;</li>
1.114 avankest 1799: <li><code>overrideMimeType</code> to fix up MIME types;</li>
1.87 avankest 1800: <li><code>getRequestHeader()</code> and
1801: <code>removeRequestHeader()</code>.</li>
1.29 avankest 1802: </ul>
1.248 avankest 1803:
1.29 avankest 1804:
1.203 avankest 1805:
1.248 avankest 1806:
1807:
1.203 avankest 1808:
1.248 avankest 1809: <h2 class="no-num" id="references">References</h2>
1.203 avankest 1810:
1.177 avankest 1811: <p>Unless marked "Non-normative" these references are normative.</p>
1.11 avankest 1812:
1.6 avankest 1813: <dl>
1.230 avankest 1814: <dt>[<dfn id="ref-cookies">COOKIES</dfn>]</dt>
1.268 avankest 1815: <dd><cite><a href="http://tools.ietf.org/html/draft-ietf-httpstate-cookie">HTTP
1816: State Management Mechanism</a></cite> (work in progress), A. Barth. IETF.</dd>
1.203 avankest 1817:
1.248 avankest 1818:
1819:
1.155 avankest 1820: <dt>[<dfn id="ref-dom2events">DOM2Events</dfn>]</dt>
1821: <dd><cite><a href="http://www.w3.org/TR/DOM-Level-2-Events/">Document
1.267 avankest 1822: Object Model (DOM) Level 2 Events Specification</a></cite>, T. Pixley.
1823: W3C.</dd>
1.155 avankest 1824:
1.145 avankest 1825: <dt>[<dfn id="ref-dom3core">DOM3Core</dfn>]</dt>
1.11 avankest 1826: <dd><cite><a href="http://www.w3.org/TR/DOM-Level-3-Core">Document Object
1.92 avankest 1827: Model (DOM) Level 3 Core Specification</a></cite>, A. Le Hors, P. Le
1.267 avankest 1828: Hégaret, L. Wood, G. Nicol, J. Robie, M. Champion, S. Byrne.
1829: W3C.</dd>
1.11 avankest 1830:
1.117 avankest 1831: <dt>[<dfn id="ref-ecmascript">ECMAScript</dfn>]</dt>
1.92 avankest 1832: <dd><cite><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">ECMAScript
1.267 avankest 1833: Language Specification</a></cite>. ECMA.</dd>
1.248 avankest 1834:
1835:
1.171 avankest 1836:
1.145 avankest 1837: <dt>[<dfn id="ref-html5">HTML5</dfn>]</dt>
1.250 avankest 1838: <dd><cite><a href="http://www.w3.org/html/wg/html5/">HTML5</a></cite>
1.267 avankest 1839: (work in progress), I. Hickson. W3C.</dd>
1.250 avankest 1840: <dd><cite><a href="http://www.whatwg.org/specs/html5/current-work/">HTML5</a></cite>
1.267 avankest 1841: (work in progress), I. Hickson. WHATWG.</dd>
1.198 avankest 1842:
1843: <dt>[<dfn id="ref-httpverbsec">HTTPVERBSEC</dfn>]</dt>
1.248 avankest 1844: <dd>(Non-normative)
1845: <cite><a href="http://www.kb.cert.org/vuls/id/867593">Multiple vendors'
1846: web servers enable HTTP TRACE method by default</a></cite>, US-CERT.</dd>
1847: <dd>(Non-normative)
1848: <cite><a href="http://www.kb.cert.org/vuls/id/288308">Microsoft Internet
1849: Information Server (IIS) vulnerable to cross-site scripting via HTTP
1850: TRACK method</a></cite>, US-CERT.</dd>
1851: <dd>(Non-normative)
1852: <cite><a href="http://www.kb.cert.org/vuls/id/150227">HTTP proxy default
1853: configurations allow arbitrary TCP connections</a></cite>, US-CERT.</dd>
1854:
1855:
1856:
1857: <dt>[<dfn id="ref-rfc2046">RFC2046</dfn>]</dt>
1858: <dd><cite><a href="http://ietf.org/rfc/rfc2046">Multipurpose Internet Mail
1859: Extensions (MIME) Part Two: Media Types</a></cite>, N. Freed, N.
1.267 avankest 1860: Borenstein. IETF.</dd>
1.198 avankest 1861:
1.145 avankest 1862: <dt>[<dfn id="ref-rfc2119">RFC2119</dfn>]</dt>
1.117 avankest 1863: <dd><cite><a href="http://ietf.org/rfc/rfc2119">Key words for use in RFCs to
1.267 avankest 1864: Indicate Requirement Levels</a></cite>, S. Bradner. IETF.</dd>
1.12 avankest 1865:
1.248 avankest 1866: <dt>[<dfn id="rfc-rfc2616">RFC2616</dfn>]</dt>
1.11 avankest 1867: <dd><cite><a href="http://ietf.org/rfc/rfc2616">Hypertext Transfer Protocol
1.92 avankest 1868: -- HTTP/1.1</a></cite>, R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L.
1.267 avankest 1869: Masinter, P. Leach, T. Berners-Lee. IETF.</dd>
1.12 avankest 1870:
1.37 avankest 1871: <dt>[<dfn id="ref-rfc2617">RFC2617</dfn>]</dt>
1.11 avankest 1872: <dd><cite><a href="http://ietf.org/rfc/rfc2617">HTTP Authentication: Basic
1.92 avankest 1873: and Digest Access Authentication</a></cite>, P. Hallam-Baker, J.
1.267 avankest 1874: Hostetler, S. Lawrence, P. Leach, A. Luotonen, L. Stewart. IETF.</dd>
1.12 avankest 1875:
1.37 avankest 1876: <dt>[<dfn id="ref-rfc3986">RFC3986</dfn>]</dt>
1.11 avankest 1877: <dd><cite><a href="http://ietf.org/rfc/rfc3986">Uniform Resource Identifier
1.267 avankest 1878: (URI): Generic Syntax</a></cite>, T. Berners-Lee, R. Fielding, L.
1879: Masinter. IETF.</dd>
1.184 avankest 1880:
1.248 avankest 1881: <dt>[<dfn id=ref-rfc3987>RFC3987</dfn>]</dt>
1882: <dd><cite><a href="http://ietf.org/rfc/rfc3987">Internationalized
1.267 avankest 1883: Resource Identifiers (IRIs)</a></cite>, M. Duerst, M. Suignard.
1884: IETF.</dd>
1.248 avankest 1885:
1.203 avankest 1886: <dt>[<dfn id="ref-webidl">WebIDL</dfn>]</dt>
1.200 avankest 1887: <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web
1.267 avankest 1888: IDL</a></cite> (work in progress), C. McCormack. W3C.</dd> <!-- XXX add Sam -->
1.181 avankest 1889:
1.92 avankest 1890: <dt>[<dfn id="ref-xml">XML</dfn>]</dt>
1891: <dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup Language
1.267 avankest 1892: (XML) 1.0</a></cite>, T. Bray, J. Paoli, C. Sperberg-McQueen, E. Maler,
1893: F. Yergeau. W3C.</dd>
1894: <dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in
1895: XML</a></cite>, T. Bray, D. Hollander, A. Layman, R. Tobin, H. S.
1896: Thompson. W3C.</dd>
1.1 avankest 1897: </dl>
1.11 avankest 1898:
1.203 avankest 1899:
1900:
1.130 avankest 1901: <h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
1.11 avankest 1902:
1.159 avankest 1903: <p>The editor would like to thank
1.12 avankest 1904:
1.163 avankest 1905: Addison Phillips,
1.159 avankest 1906: Ahmed Kamel,
1907: Alex Hopmann,
1908: Alex Vincent,
1909: Alexey Proskuryakov,
1910: Asbjørn Ulsberg,
1911: Boris Zbarsky,
1912: Björn Höhrmann,
1913: Cameron McCormack,
1914: Christophe Jolif,
1915: Charles McCathieNevile,
1916: Dan Winship,
1.248 avankest 1917: David Andersson,
1.159 avankest 1918: David Håsäther,
1.248 avankest 1919: David Levin,
1.159 avankest 1920: Dean Jackson,
1921: Denis Sureau,
1922: Doug Schepers,
1923: Douglas Livingstone,
1924: Elliotte Harold,
1925: Eric Lawrence,
1.196 avankest 1926: Erik Dahlström,
1.163 avankest 1927: Geoffrey Sneddon,
1.159 avankest 1928: Gideon Cohn,
1929: Gorm Haug Eriksen,
1.247 avankest 1930: Håkon Wium Lie,
1.159 avankest 1931: Hallvord R. M. Steen,
1.247 avankest 1932: Huub Schaeks,
1.159 avankest 1933: Ian Davis,
1934: Ian Hickson,
1935: Ivan Herman,
1936: Jeff Walden,
1937: Jens Lindström,
1938: Jim Deegan,
1939: Jim Ley,
1940: Joe Farro,
1941: Jonas Sicking,
1942: Julian Reschke,
1943: Karl Dubost,
1.175 avankest 1944: Lachlan Hunt,
1.159 avankest 1945: Maciej Stachowiak,
1946: Magnus Kristiansen,
1947: Marc Hadley,
1948: Marcos Caceres,
1949: Mark Baker,
1.203 avankest 1950: Mark Birbeck,
1.159 avankest 1951: Mark Nottingham,
1.267 avankest 1952: Mark S. Miller,
1.248 avankest 1953: Martin Hassman,
1.159 avankest 1954: Mohamed Zergaoui,
1.256 avankest 1955: Olli Pettay,
1.159 avankest 1956: Pawel Glowacki,
1.231 avankest 1957: Peter Michaux,
1.264 avankest 1958: Philip Taylor,
1.159 avankest 1959: Robin Berjon,
1.248 avankest 1960: Rune Halvorsen,
1.159 avankest 1961: Ruud Steltenpool,
1962: Simon Pieters,
1963: Stewart Brodie,
1964: Sunava Dutta,
1.186 avankest 1965: Thomas Roessler,
1.203 avankest 1966: Tom Magliery, and
1.159 avankest 1967: Zhenbin Xu
1.181 avankest 1968:
1.159 avankest 1969: for their contributions to this specification.</p>
1.12 avankest 1970:
1.1 avankest 1971: <p>Special thanks to the Microsoft employees who first implemented the
1.143 avankest 1972: <code title="">XMLHttpRequest</code> interface, which was first widely
1973: deployed by the Windows Internet Explorer browser.</p>
1.12 avankest 1974:
1.143 avankest 1975: <p>Special thanks also to the WHATWG for drafting an initial version of
1976: this specification in their Web Applications 1.0 document (now renamed to
1.250 avankest 1977: HTML5). [<cite><span>HTML5</span></cite>]</p>
1.12 avankest 1978:
1.143 avankest 1979: <p>Thanks also to all those who have helped to improve this specification
1980: by sending suggestions and corrections. (Please, keep bugging us with your
1.22 avankest 1981: issues!)</p>
1.1 avankest 1982: </body>
1983: </html>
1.211 avankest 1984:
Webmaster