This topic describes configuration options for using the HTTP 1.0 transport in Client tools.
In this section:
| Table of Contents | ||
|---|---|---|
|
...
The Endpoint option is available for SOAP Clients. Choose a definition from the dropdown menu:
- WSDL: Specifies the endpoint defined in the WSDL.
- Default: Specifies the endpoint defined in the Test or Action Suite.
- Custom: Allows you to set any custom endpoint.
- UDDI serviceKey: Describes what UDDI serviceKey is used to reference this server endpoint in the UDDI registry specified in the Preferences panel’s WSDL/UDDI tab.
...
The Router Endpoint option is available for Messaging Clients. It specifies the endpoint URL for the server. Choose Fixed from the dropdown menu and manually specify the URL in the field provided. The endpoint can be specified as a fixed a fixed value, parameterized value, or scripted value. For For details about scripting values, see Extensibility and Scripting Basics.
...
Specifies Keep-Alive or Close connections.
- Keep-Alive connection: Adds a "Connection: Keep-Alive" header to request a keep-alive connection if the server supports it. This is required for NTLM and Digest HTTP authentication.
- Close connection (default): Outputs no additional HTTP headers and performs a regular HTTP 1.0 exchange. This is the default behavior for HTTP 1.0.
The connection setting enabled will also be reused for a single invocation of a test suite from the GUI or the command line.
Redirect Settings
Enable the Follow HTTP redirects option for messaging clients to automatically follow HTTP redirects. Disable this option if you want to perform an action or validation on the original request/response traffic (instead of working only with the final request/response pair).
...
Compression settings are available for messaging clients. They specify whether to compress requests and decompress responses. You can enable the following compression setting options:
- Gzip request payload: Gzips the request payloads being sent over the network. Data sent to attached tools will not be compressed. Note that compression does not apply to SOAP Clients configured to send attachments or in MTOM mode.
- Decompress gzip-encoded response payload: Decompresses response payloads that have "Content-Encoding: gzip" as a header field. Attached tools will receive the uncompressed data.
...
| Info | ||
|---|---|---|
| ||
URL query parameters are formatted according to the "application/x-www-form-urlencoded" content type. Space characters are replaced with '+'. Non alpha numeric -alphanumeric characters are replaced with a percent sign followed by two hexadecimal digits representing the character code. Names and values are separated by '=' and name-value pairs are separated by '&'. If you want to use a different format, query parameters can also be specified directly at the end of the tool's endpoint URL (instead of in the URL Parameters section). For example, you could use |
...
Allows you to select an authentication method for the tool. Unless otherwise specified, the default authentication method set up for the test suite is used (see Configuring Test Suite Properties), but you can change it by selecting Custom from the first dropdown menu and choosing the desired option from the next dropdown. Options include:
...
This HTTP header is sent for SOAP 1.1 only. It is set in the SOAPAction field of the General settings.
Authorization
This header is constructed automatically based on the Authentication and OAuth settings specified in client options (HTTP Options > Security > Authentication). The value for NTLM, Digest, and Kerberos authentication will vary depending on various factors, including dynamically generated challenge responses and security tokens.
...