nsIXMLHttpRequest

  • Revision slug: nsIXMLHttpRequest
  • Revision title: nsIXMLHttpRequest
  • Revision id: 59573
  • Created:
  • Creator: Cancerbero sgx
  • Is current revision? No
  • Comment /* overrideMimeType */

Revision Content

page created by Sebastián (Cancerbero) Gurin sgurin@(nospam)montevideo.com.uy

Summary

Mozilla's XMLHttpRequest is modelled after Microsoft's IXMLHttpRequest object. The goal has been to make Mozilla's version match Microsoft's version as closely as possible, but there are bound to be some differences.

In general, Microsoft's documentation for IXMLHttpRequest can be used. Mozilla's interface definitions provide some additional documentation. The web page to look at is http://www.mozilla.org/xmlextras/.

Mozilla's XMLHttpRequest object can be created in JavaScript like this:

  new XMLHttpRequest()

compare to Internet Explorer:

  new ActiveXObject("Msxml2.XMLHTTP")

From JavaScript, the methods and properties visible in the XMLHttpRequest object are a combination of nsIXMLHttpRequest and nsIJSXMLHttpRequest there is no need to differentiate between those interfaces.

From native code, the way to set up onload and onerror handlers is a bit different. Here is a comment from Johnny Stenback <jst@netscape.com>:

The mozilla implementation of nsIXMLHttpRequest implements the interface nsIDOMEventTarget and that's how you're supported to add event listeners. Try something like this: nsCOMPtr<nsIDOMEventTarget> target(do_QueryInterface(myxmlhttpreq)); target->AddEventListener(NS_LITERAL_STRING("load"), mylistener, PR_FALSE) where mylistener is your event listener object that implements the interface nsIDOMEventListener. The 'onload', 'onerror', and 'onreadystatechange' attributes moved to nsIJSXMLHttpRequest, but if you're coding in C++ you should avoid using those.

Though actually, if you use addEventListener from C++ weird things will happen too, since the result will depend on what JS happens to be on the stack when you do it....

Conclusion: Do not use event listeners on XMLHttpRequest from C++, unless you're aware of all the security implications. And then think twice about it.

Interface Code

 [scriptable, uuid(7b3b3c62-9d53-4abc-bc89-c33ce78f439f)]
 interface nsIXMLHttpRequest : nsISupports
 {
   //attribtues
   readonly attribute nsIChannel channel;
   readonly attribute nsIDOMDocument responseXML;
   readonly attribute AString responseText;
   readonly attribute unsigned long status;
   readonly attribute AUTF8String statusText;
   readonly attribute long readyState;
   attribute boolean multipart;
   //methods
   void   abort();
   string getAllResponseHeaders();
   ACString getResponseHeader(in AUTF8String header);
   [noscript] void   openRequest(in AUTF8String method,
                                 in AUTF8String url,
                                 in boolean async,
                                 in AString user,
                                 in AString password);
   void   open(in AUTF8String method, in AUTF8String url);
   void   send(in nsIVariant body);
   void   overrideMimeType(in AUTF8String mimetype);
 };

Attributes

channel

 readonly attribute nsIChannel channel;

The request uses a channel in order to perform the request. This attribute represents the channel used for the request. NULL if the channel has not yet been created.

In a multipart request case, this is the initial channel, not the different parts in the multipart request.

Mozilla only. Requires elevated privileges to access.

responseXML

 readonly attribute nsIDOMDocument responseXML

The response to the request is parsed as if it were a text/xml stream. This attributes represents the response as a DOM Document object. NULL if the request is unsuccessful or has not yet been sent.

responseText

 readonly attribute AString responseText;

The response to the request as text. NULL if the request is unsuccessful or has not yet been sent.

status

 readonly attribute unsigned long status;

The status of the response to the request for HTTP requests.

statusText

 readonly attribute AUTF8String statusText;

The string representing the status of the response for HTTP requests.

readyState

 readonly attribute long readyState;

The state of the request. Possible values:

0 UNINITIALIZED open() has not been called yet. 1 LOADING send() has not been called yet. 2 LOADED send() has been called, headers and status are available. 3 INTERACTIVE Downloading, responseText holds the partial data. 4 COMPLETED Finished with all operations.

multipart

 attribute boolean multipart;

Set to true if the response is expected to be a stream of possibly multiple (XML) documents. If set to true, the content type of the initial response must be multipart/x-mixed-replace or an error will be triggerd. All requests must be asynchronous.

This enables server push. For each XML document that's written to this request, a new XML DOM document is created and the onload handler is called inbetween documents. Note that when this is set, the onload handler and other event handlers are not reset after the first XML document is loaded, and the onload handler will be called as each part of the response is received.

Methods

abort

 void   abort();

If the request has been sent already, this method will abort the request.

getAllResponseHeaders

 string getAllResponseHeaders();

Returns all of the response headers as a string for HTTP requests.

Note that this will return all the headers from the *current* part of a multipart request, not from the original channel. Returns A string containing all of the response headers or NULL if the response has not yet been received.

getResponseHeader

 ACString getResponseHeader(in AUTF8String header);

Returns the text of the header with the specified name for HTTP requests.

header - The name of the header to retrieve

Returns a string containing the text of the header specified or NULL if the response has not yet been received or the header does not exist in the response.

openRequest

  [noscript] void   openRequest(in AUTF8String method,
                                in AUTF8String url,
                                in boolean async,
                                in AString user,
                                in AString password);

Native (non-script) method to initialize a request. Note that the request is not sent until the send method is invoked.

If there is an "active" request (that is, if open() or openRequest() has been called already), this is equivalent to calling abort().

method - The HTTP method, for example "POST" or "GET". Ignored if the URL is not a HTTP(S) URL. url - The URL to which to send the request. async - Whether the request is synchronous or asynchronous i.e. whether send returns only after the response is received or if it returns immediately after sending the request. In the latter case, notification of completion is sent through the event listeners. This argument must be true if the multipart attribute has been set to true, or an exception will be thrown. user - A username for authentication if necessary. password - A password for authentication if necessary.

open

 void   open(in AUTF8String method, in AUTF8String url);

Meant to be a script-only method for initializing a request. The parameters are similar to the ones detailed in the description of openRequest, but the last 3 are optional.

If there is an "active" request (that is, if open() or openRequest() has been called already), this is equivalent to calling abort().

method - The HTTP method - either "POST" or "GET". Ignored if the URL is not a HTTP URL. url - The URL to which to send the request. async - (optional) Whether the request is synchronous or asynchronous i.e. whether send returns only after the response is received or if it returns immediately after sending the request. In the latter case, notification of completion is sent through the event listeners. The default value is true. This argument must be true if the multipart attribute has been set to true, or an exception will be thrown. user - (optional) A username for authentication if necessary. The default value is the empty string password - (optional) A password for authentication if necessary. The default value is the empty string

send

 void   send(in nsIVariant body);

Sends the request. If the request is asynchronous, returns immediately after sending the request. If it is synchronous returns only after the response has been received.

All event listeners must be set before calling send().

After the initial response, all event listeners will be cleared.

body - Either an instance of nsIDOMDocument, nsIInputStream or a string (nsISupportsString in the native calling case). This is used to populate the body of the HTTP request if the HTTP request method is "POST". If the parameter is a nsIDOMDocument, it is serialized. If the parameter is a nsIInputStream, then it must be compatible with nsIUploadChannel.setUploadStream, and a Content-Length header will be added to the HTTP request with a value given by nsIInputStream.available. Any headers included at the top of the stream will be treated as part of the message body. The MIME type of the stream should be specified by setting the Content- Type header via the setRequestHeader method before calling send.

setRequestHeader

 void   setRequestHeader(in AUTF8String header, in AUTF8String value);

Sets a HTTP request header for HTTP requests. You must call open before setting the request headers.

header - The name of the header to set in the request. value - The body of the header.

overrideMimeType

 void   overrideMimeType(in AUTF8String mimetype);

Override the mime type returned by the server (if any). This may be used, for example, to force a stream to be treated and parsed as text/xml, even if the server does not report it as such. This must be done before the send method is invoked. mimetype - The type used to override that returned by the server (if any).

{{ wiki.languages( { "pl": "pl/NsIXMLHttpRequest" } ) }}

Revision Source

<p><span class="comment">page created by Sebastián (Cancerbero) Gurin sgurin@(nospam)montevideo.com.uy</span>
</p>
<h3 name="Summary">Summary</h3>
<p>Mozilla's XMLHttpRequest is modelled after Microsoft's IXMLHttpRequest object. The goal has been to make Mozilla's version match Microsoft's version as closely as possible, but there are bound to be some differences.
</p><p>In general, Microsoft's documentation for IXMLHttpRequest can be used. Mozilla's interface definitions provide some additional documentation. The web page to look at is http://www.mozilla.org/xmlextras/.
</p><p>Mozilla's XMLHttpRequest object can be created in JavaScript like this:
</p>
<pre class="eval">  new XMLHttpRequest()
</pre>
<p>compare to Internet Explorer:
</p>
<pre class="eval">  new ActiveXObject("Msxml2.XMLHTTP")
</pre>
<p>From JavaScript, the methods and properties visible in the XMLHttpRequest object are a combination of nsIXMLHttpRequest and <a href="en/NsIJSXMLHttpRequest">nsIJSXMLHttpRequest</a> there is no need to differentiate between those interfaces.
</p><p>From native code, the way to set up onload and onerror handlers is a bit different. Here is a comment from Johnny Stenback &lt;jst@netscape.com&gt;:
</p>
<blockquote>The mozilla implementation of nsIXMLHttpRequest implements the interface  nsIDOMEventTarget and that's how you're supported to add event listeners. Try something like this:

   nsCOMPtr&lt;nsIDOMEventTarget&gt; target(do_QueryInterface(myxmlhttpreq));
   target-&gt;AddEventListener(NS_LITERAL_STRING("load"), mylistener, PR_FALSE)

where mylistener is your event listener object that implements the interface nsIDOMEventListener.

The 'onload', 'onerror', and 'onreadystatechange' attributes moved to nsIJSXMLHttpRequest, but if you're coding in C++ you should avoid using those.</blockquote>
<p>Though actually, if you use addEventListener from C++ weird things will happen too, since the result will depend on what JS happens to be on the stack when you do it....
</p><p>Conclusion: Do not use event listeners on XMLHttpRequest from C++, unless you're aware of all the security implications. And then think twice about it.
</p>
<h3 name="Interface_Code">Interface Code</h3>
<pre class="eval"> [scriptable, uuid(7b3b3c62-9d53-4abc-bc89-c33ce78f439f)]
 interface nsIXMLHttpRequest : nsISupports
 {
   //attribtues
   readonly attribute nsIChannel channel;
   readonly attribute nsIDOMDocument responseXML;
   readonly attribute AString responseText;
   readonly attribute unsigned long status;
   readonly attribute AUTF8String statusText;
   readonly attribute long readyState;
   attribute boolean multipart;
   //methods
   void   abort();
   string getAllResponseHeaders();
   ACString getResponseHeader(in AUTF8String header);
   [noscript] void   openRequest(in AUTF8String method,
                                 in AUTF8String url,
                                 in boolean async,
                                 in AString user,
                                 in AString password);
   void   open(in AUTF8String method, in AUTF8String url);
   void   send(in nsIVariant body);
   void   overrideMimeType(in AUTF8String mimetype);
 };
</pre>
<h3 name="Attributes">Attributes</h3>
<h4 name="channel">channel</h4>
<pre class="eval"> readonly attribute nsIChannel channel;
</pre>
<p>The request uses a channel in order to perform the request.  This attribute represents the channel used for the request.  NULL if the channel has not yet been created.
</p><p>In a multipart request case, this is the initial channel, not the different parts in the multipart request.
</p><p>Mozilla only. Requires elevated privileges to access.
</p>
<h4 name="responseXML">responseXML</h4>
<pre class="eval"> readonly attribute nsIDOMDocument responseXML
</pre>
<p>The response to the request is parsed as if it were a text/xml stream. This attributes represents the response as a DOM Document object. NULL if the request is unsuccessful or has not yet been sent.
</p>
<h4 name="responseText">responseText</h4>
<pre class="eval"> readonly attribute AString responseText;
</pre>
<p>The response to the request as text. NULL if the request is unsuccessful or has not yet been sent.
</p>
<h4 name="status">status</h4>
<pre class="eval"> readonly attribute unsigned long status;
</pre>
<p>The status of the response to the request for HTTP requests.
</p>
<h4 name="statusText">statusText</h4>
<pre class="eval"> readonly attribute AUTF8String statusText;
</pre>
<p>The string representing the status of the response for HTTP requests.
</p>
<h4 name="readyState">readyState</h4>
<pre class="eval"> readonly attribute long readyState;
</pre>
<p>The state of the request.
Possible values:
</p>
<blockquote>
0 UNINITIALIZED open() has not been called yet.
1 LOADING       send() has not been called yet.
2 LOADED        send() has been called, headers and status are available.
3 INTERACTIVE   Downloading, responseText holds the partial data.
4 COMPLETED     Finished with all operations.</blockquote>
<h4 name="multipart">multipart</h4>
<pre class="eval"> attribute boolean multipart;
</pre>
<p>Set to true if the response is expected to be a stream of possibly multiple (XML) documents. If set to true, the content type of the initial response must be multipart/x-mixed-replace or an error will be triggerd. All requests must be asynchronous.
</p><p>This enables server push. For each XML document that's written to this request, a new XML DOM document is created and the onload handler is called inbetween documents. Note that when this is set, the onload handler and other event handlers are not reset after the first XML document is loaded, and the onload handler will be called as each part of the response is received.
</p>
<h3 name="Methods">Methods</h3>
<h4 name="abort">abort</h4>
<pre class="eval"> void   abort();
</pre>
<p>If the request has been sent already, this method will abort the request.
</p>
<h4 name="getAllResponseHeaders">getAllResponseHeaders</h4>
<pre class="eval"> string getAllResponseHeaders();
</pre>
<p>Returns all of the response headers as a string for HTTP requests.
</p><p>Note that this will return all the headers from the *current* part of a multipart request, not from the original channel.
<code>Returns</code> A string containing all of the response headers or NULL if the response has not yet been received.
</p>
<h4 name="getResponseHeader">getResponseHeader</h4>
<pre class="eval"> ACString getResponseHeader(in AUTF8String header);
</pre>
<p>Returns the text of the header with the specified name for HTTP requests.
</p><p><code>header</code> - The name of the header to retrieve
</p><p>Returns a string containing the text of the header specified or NULL if the response has not yet been received or the header does not exist in the response.
</p>
<h4 name="openRequest">openRequest</h4>
<pre class="eval">  [noscript] void   openRequest(in AUTF8String method,
                                in AUTF8String url,
                                in boolean async,
                                in AString user,
                                in AString password);
</pre>
<p>Native (non-script) method to initialize a request. Note that the request is not sent until the <code>send</code> method is invoked.
</p><p>If there is an "active" request (that is, if open() or openRequest() has been called already), this is equivalent to calling abort().
</p><p><code>method</code> - The HTTP method, for example "POST" or "GET". Ignored if the URL is not a HTTP(S) URL.
<code>url</code> - The URL to which to send the request.
<code>async</code> - Whether the request is synchronous or asynchronous i.e. whether send returns only after the response is received or if it returns immediately after sending the request. In the latter case, notification of completion is sent through the event listeners. This argument must be true if the multipart attribute has been set to true, or an exception will be thrown.
<code>user</code> - A username for authentication if necessary.
<code>password</code> - A password for authentication if necessary.
</p>
<h4 name="open">open</h4>
<pre class="eval"> void   open(in AUTF8String method, in AUTF8String url);
</pre>
<p>Meant to be a script-only method for initializing a request. The parameters are similar to the ones detailed in the description of <code>openRequest</code>, but the last 3 are optional.
</p><p>If there is an "active" request (that is, if <code>open()</code> or <code>openRequest()</code> has been called already), this is equivalent to calling <code>abort()</code>.
</p><p><code>method</code> - The HTTP method - either "POST" or "GET". Ignored if the URL is not a HTTP URL.
<code>url</code> - The URL to which to send the request.
<code>async</code> - (optional) Whether the request is synchronous or asynchronous i.e. whether send returns only after the response is received or if it returns immediately after sending the request. In the latter case, notification of completion is sent through the event listeners. The default value is true. This argument must be true if the multipart attribute has been set to true, or an exception will be thrown.
<code>user</code> - (optional) A username for authentication if necessary. The default value is the empty string
<code>password</code> - (optional) A password for authentication if necessary. The default value is the empty string
</p>
<h4 name="send">send</h4>
<pre class="eval"> void   send(in nsIVariant body);
</pre>
<p>Sends the request. If the request is asynchronous, returns immediately after sending the request. If it is synchronous returns only after the response has been received.
</p><p>All event listeners must be set before calling send().
</p><p>After the initial response, all event listeners will be cleared.
</p><p><code>body</code> - Either an instance of nsIDOMDocument, nsIInputStream or a string (nsISupportsString in the native calling case). This is used to populate the body of the HTTP request if the HTTP request method is "POST". If the parameter is a nsIDOMDocument, it is serialized. If the parameter is a nsIInputStream, then it must be compatible with nsIUploadChannel.setUploadStream, and a Content-Length header will be added to the HTTP request with a value given by nsIInputStream.available.  Any headers included at the top of the stream will be treated as part of the message body.  The MIME type of the stream should be specified by setting the Content- Type header via the setRequestHeader method before calling send.
</p>
<h4 name="setRequestHeader">setRequestHeader</h4>
<pre class="eval"> void   setRequestHeader(in AUTF8String header, in AUTF8String value);
</pre>
<p>Sets a HTTP request header for HTTP requests. You must call open before setting the request headers.
</p><p><code>header</code> - The name of the header to set in the request.
<code>value</code> - The body of the header.
</p>
<h4 name="overrideMimeType">overrideMimeType</h4>
<pre class="eval"> void   overrideMimeType(in AUTF8String mimetype);
</pre>
<p>Override the mime type returned by the server (if any). This may be used, for example, to force a stream to be treated and parsed as text/xml, even if the server does not report it as such. This must be done before the <code>send</code> method is invoked.
<code>mimetype</code> - The type used to override that returned by the server (if any).
</p>{{ wiki.languages( { "pl": "pl/NsIXMLHttpRequest" } ) }}
Revert to this revision