HTTP transport policy settings
Use this page to define HTTP transport policy configuration. HTTP features and HTTP connection policies are applied to outbound messages. Any changes to the HTTP transport policy from this console page affects all JAX-WS applications to which this custom HTTP transport policy is attached.
From the admin console, click Services > Policy sets > Application policy sets > policy_set_name > HTTP transport, where policy_set_name, applies to any policy set containing HTTP transport policy.
This administrative console page applies only to JAX-WS applications.
We can only configure a policy through a policy set. Therefore, before we can configure the HTTP transport policy, a policy set must exist containing the HTTP transport policy.
The WSHTTPS default policy set is provided with the application server and it contains the HTTP transport policy, the SSL transport policy and the WS-Addressing policy. The provided default WSHTTPS policy set is read only and it cannot be edited. To customize a policy set containing the HTTP transport policy, first create a copy of the WSHTTPS default policy set or create a new policy set and add the HTTP transport policy to the new policy set.
After you customize values for the HTTP transport policy, these values now apply for our policy set containing that custom HTTP transport policy. Attach this policy set containing our customized HTTP transport policy to the application, its services, endpoints, or operations. This change affects all JAX-WS applications to which that policy set is attached. To learn more about attaching policy sets to applications, see the documentation for managing policy sets for service providers and service clients at the application level.
Protocol version
Version of HTTP protocol to use. Use this list to specify the version of HTTP protocol. The default is HTTP 1.1. The HTTP 1.0 value is also a valid option.
Some of the remaining options on the HTTP Transport panel only work with HTTP Version 1.1. The following brief descriptions compare these options:
- HTTP 1.0
- Allows messages to be in MIME-like format, containing meta information about the data transferred and modifiers on the request, response, or both. However, HTTP 1.0 does not sufficiently address the effects of hierarchical proxies, caching, the need for persistent connections, or virtual hosts.
- HTTP 1.1
- Enable each of two communicating applications to determine the true capabilities or the other. This protocol includes more stringent requirements than HTTP 1.0 to ensure reliable implementation of features.
Session enabled
Specifies whether the HTTP session is enabled when a message is sent. Select this check box to enable an HTTP session.
If this property is used within a policy set that is attached to a service client, then it indicates whether HTTP session information is propagated to subsequent requests invoked by the same client application. If the property is enabled, the HTTP session information is returned to the service client in a response message is sent in subsequent requests invoked using the same RequestContext object.
If this property is used within a policy set that is attached to a service provider, then it indicates whether or not a new HTTP session is created when a request is being processed. If the property is enabled, then as a request is being processed, a new HTTP session is created if one does not already exist. This HTTP session information is then returned to the service client in the response message.
Enable chunked transfer encoding
Specifies whether chunked transfer encoding is enabled when a message is sent. Select this check box to enable a chunked transfer encoding. This option is only available if we select HTTP 1.1 in the Protocol version field. This option is disabled if we selected the HTTP 1.0 protocol.
The default for this property is true.
Send expect "100-request" header
Specifies whether the expect "100-request" header is enabled when a message is sent. Select this check box to enable the expect "100-request" header. This option is only available if we selected HTTP 1.1 in the Protocol version field. This option is disabled if we selected the HTTP 1.0 protocol.
The purpose of the 100 status is to allow a client that is sending a request message with a request body to determine if the origin server accepts the request, based on the request headers, before the client sends the request body. In some cases, we might not want the client to send the body if the server rejects the message without looking at the body.
The Expect request-header field is used to indicate that particular server behaviors are required by the client. A server that cannot comply with any of the expectation values in the Expect field if a request responds with an appropriate error status.
Accept URL redirection automatically
Specifies whether the automatic URL redirection is accepted when a message is sent. Select this check box to enable a URL that has been automatically redirected to be accepted.
Compress request content
Specifies whether the request content is compressed when a message is sent. Content coding is used to allow a document to be compressed without losing the identity of its underlying media type and without loss of information. Select this check box to enable request content to compress. Clicking the Compress request content button enables the Compression format option to select the compression method. The default value for the compression format is gzip.
Compress response content
Specifies whether the response content is compressed when a message is sent. Content coding is used to allow a document to be compressed without losing the identity of its underlying media type and without loss of information. Select this check box to enable response content to compress. Clicking the Compress response content button enables the Compression format option as he compression method. The default value for the compression format is gzip.
Read timeout
Length of time, in seconds, for the Web services client to completely read the SOAP response. If the read process does not complete within the specified time, a SOAP fault error is generated on the client machine.
Write timeout
Length of time, in seconds, for the write action to time out when a message is sent. Time, in seconds, to enable the write to time out length of time.
Connection timeout
Length of time, in seconds, for the connection to time out when a message is sent. Time, in seconds, to enable the connection to time out length of time.
Use persistent connection
Specifies whether a persistent connection is used when a message is sent. Select this check box to enable use of a persistent connection. This option is only available if we selected HTTP 1.1 in the Protocol version field. This option is disabled if we selected the HTTP 1.0 protocol.
Resend enabled
Specifies whether a message can be resent. Select this check box to resend a message.
Configure the HTTP transport policy Manage policy sets Manage policy sets and bindings for service providers at the application level Manage policy sets and bindings for service clients at the application level HTTP transport bindings settings Application policy sets collection Application policy set settings Service client policy set and bindings collection Service provider policy sets and bindings collection