send Method (IXMLHTTPRequest)
A version of this page is also available for
4/8/2010
Sends an HTTP request to the server and receives a response.
Script Syntax
oXMLHttpRequest.send(varBody);
Remarks
Script Parameters
- varBody
[optional] Variant. Case-insensitive name.
Script Return Value
None.
C/C++ Syntax
HRESULT send(
VARIANT varBody
);
Remarks
C/C++Parameters
- varBody
[in, optional] The body of the message being sent with the request.
C/C++ Return Values
- S_OK
Value returned if successful.
- E_FAIL
Value returned if an error occurs.
Requirements
| Header | msxml2.h, msxml2.idl |
| Library | uuid.lib |
| Windows Embedded CE | Windows CE .NET 4.0 and later |
General Remarks
This method is synchronous or asynchronous, depending on the value of the bAsync parameter in the open Method (IXMLHTTPRequest) call. If open is called with bAsync == False, this call does not return until the entire response is received or the protocol stack times out. If open is called with bAsync == True, this call returns immediately.
This method takes one parameter, which is the requestBody to use. The acceptable VARIANT input types are BSTR, SAFEARRAY of UI1 (unsigned bytes), IDispatch to an XML Document Object Model (DOM) object, and IStream *. You can only use chunked encoding (for sending) when sending IStream * input types. The component automatically sets the Content-Length header for all but IStream * input types.
If the input type is a BSTR, the response is always encoded as UTF-8. The caller must set a Content-Type header with the appropriate content type and include a charset parameter.
If the input type is a SAFEARRAY of UI1, the response is sent as is without additional encoding. The caller must set a Content-Type header with the appropriate content type.
If the input type is an XML DOM object, the response is encoded according to the encoding attribute on the <? declaration in the document. If there is no XML declaration or encoding attribute, UTF-8 is assumed.
If the input type is an IStream *, the response is sent as is without additional encoding. The caller must set a Content-Type header with the appropriate content type.
This method applies to the following interface: