SOAP request properties define how ReadyAPI handles specific SOAP requests.
Click the image to enlarge it.
| Option | Description | ||
|---|---|---|---|
| Name | The name of the request. | ||
| Description | An arbitrary text describing the request. | ||
| Message Size | The size of the request in bytes. | ||
| Encoding |
The type of request data encoding, for example UTF-8 or iso-8859-1.
|
||
| Endpoint |
The Resource part of the target URL (including the port number).
|
||
| Timeout | The number of milliseconds to wait for the server response. If no data arrives within the specified time period, the request is considered to fail. If the value is 0 or is not specified, the wait time is infinite. | ||
| Bind Address | The network interface (an IP address), through which ReadyAPI will send the request. | ||
| Follow Redirects |
Enables handling of redirects. If true, the request will follow the redirect and return a server message. Otherwise, a redirect message will be returned.
|
||
| Follow 302 Redirect with GET |
If true, ReadyAPI uses the GET method for subsequent requests if the response has the 302 Found HTTP code.
|
||
| Username | The basic authorization username. | ||
| Password | The basic authorization password. | ||
| Domain | Optional. The basic authorization domain. | ||
| Authentication Type | The Authorizaiton type used for the request. | ||
| WSS-Password Type | The password type to use for WSS. | ||
| WSS TimeToLive | Indicates how long the WSS credentials will be valid. | ||
| SSL Keystore | Specifies the file storing private keys that are used to authorize ReadyAPI to the server. Only works for HTTPS requests. | ||
| Skip SOAP Action |
If true, excludes the action value from the request header.Example: Content-Type: application/soap+xml;charset=UTF-8;action="http://myservercom/myoperation".
|
||
| Enable MTOM |
If true, enables the MTOM packaging method for attachments.
|
||
| Force MTOM |
If true, makes MTOM packaging mandatory for all attachments.Note: You can use it even if there are no MTOM attachments. |
||
| Inline Response Attachments |
If true, displays raw response data including MIME and MTOM attachments. If false, attachments are shown in the Attachments inspector.
|
||
| Expand MTOM Attachments |
If true, MTOM attachments in responses are shown in the response body, and can be validated with assertions. If false, attachments are shown in the Attachments inspector.
|
||
| Disable Multiparts |
If true, prevents sending attachments of the same type as multipart attachments.
|
||
| Encode Attachments |
If true, ReadyAPI encodes attachments according to the service definition (WSDL). For example hex binary, or base64.
|
||
| Enable Inline Files |
If true, file data is inserted into the request message.
|
||
| Strip Whitespaces |
If true, ReadyAPI removes comments and extra whitespaces from elements and attributes. Works for request contents in the XML format.
|
||
| Remove Empty Content |
If true, ReadyAPI removes empty elements from the request. Works for request contents in the XML format.
|
||
| Entitize Properties |
If true, ReadyAPI encodes special characters. For example, HTML symbols like & or > are entitized into & or >.
|
||
| Disable Property Expansions |
If true, property expansions in the request are disabled and will be treated as plain text.
|
||
| Pretty Print |
If true, ReadyAPI uses line feeds and indentation to display XML data of the response.
|
||
| Dump File | The path to the file where responses will be saved. If empty, responses are discarded. | ||
| Max Size |
The maximum size of responses to be saved. 0 means the entire responses will be saved.
|
||
| WS-Addressing |
If true, the request uses WS-Addressing.
|
||
| WS-Reliable Messaging |
If true, the request uses WS-Reliable Messaging.
|
