Output
The output for the activity is the following.
Output Item |
Datatype |
Description |
Method |
string |
The HTTP method to use for the request. All HTTP 1.1 methods are supported. |
RequestURI |
string |
The address portion of the request. This is the portion before the question mark ( |
HTTPVersion |
string |
Version field of the HTTP request. |
PostData or BinaryContent |
string |
The message body of the HTTP request. The content of this element depends upon whether the message body is parsed. Parsing behavior is controlled by the Parse Post Method Data field on the Configuration tab). For more information, see Special Characters in HTTP Requests. |
Command |
string |
Command portion of the HTTP request. |
QueryString |
string |
The query string portion of the request. This is the portion after the question mark ( |
Header |
string |
The header of the HTTP request. |
DynamicHeaders |
complex |
The dynamic header is an additional header parameter to add runtime headers to the Outgoing Http Messages. This element is specified in the Input tab. Dynamic header consists of the following information:
The following overriding conditions can be considered:
|
Protocol |
string |
Can be either HTTP or HTTPS depending upon the protocol used by the request. |
Port |
string |
Port number on which the request was received. This is the port number configured in the HTTP Connection resource. |
mimeEnvelope |
complex |
This element contains the message attachments. This element contains a repeating element named mimePart that contains each mime attachment. |
mimeHeaders |
complex |
This element contains the mime header for each mimePart. Mime headers can contain the following information:
For more information about MIME headers and their syntax, see http://www.faqs.org/rfcs/rfc2045.html. Note: When the content type is specified as "text/*" (for example, "text/xml"), the attachment content is expected to be in either the textContent input element or the file name storing the attachment is expected to be in the fileName input element. When the content type is anything other than "text/*", the attachment content is expected to be in either the binaryContent input element or the file name storing the attachment is expected to be in the fileName input element.
|
binaryContent | textContent | fileName |
choice |
This element contains the mime attachment. The element can be one of the following:
|
Headers |
complex |
The fields of the header specified on the Headers tab. For more information about these items, see the description of the Headers tab. |
parameters |
complex |
Parameters for the incoming request. These parameters are configured in the Parameters field on the Configuration tab. When the Parse Post Method Data field on the Configuration tab is checked, the parameters include the parameters in the query string and message body of the incoming HTTP request. When the Parse Post Method Data field is unchecked, the parameters only include the query string of the incoming request. |