This tab enables you to configure certain advanced features of the
Connect to URL filter. The following configuration
options are available:
Handles Redirects:
Specifies whether the Enterprise Gateway handles HTTP redirects,
and connects to the redirect URL specified in the HTTP response.
This setting is enabled by default.
Send via Proxy:
Select this option if the Enterprise Gateway must connect to the destination Web
Service through an HTTP proxy. In this case, the Enterprise Gateway includes the
full URL of the destination Web Service in the request line of the HTTP
request. For example, if the destination Web Service resides at
http://localhost:8080/services , the request
line is as follows:
| | |
|
POST http://localhost:8080/services HTTP/1.1
| |
| | |
|
If the Enterprise Gateway was not routing through a proxy, the request line is
as follows:
Proxy Server:
You can configure a specific proxy server to use for the connection in the
Proxy Server field. Click the button next to this field, and
select an existing proxy server in the dialog. You must have already configured
the proxy server on the External Connections tab.
For more details, see the Proxy
Servers topic.
Transparent Proxy (present client's IP address to server)
Enables the use of the Enterprise Gateway as a transparent proxy
on Linux systems with the TPROXY kernel option set. When selected,
the IP address of the original client connection that caused the circuit to be
invoked is used as the local address of the connection to the destination server.
For more details, see Configuring a
Transparent Proxy.
Ciphers:
The Ciphers field enables the administrator to specify
the ciphers that Enterprise Gateway supports. The Enterprise Gateway sends this list of
supported ciphers to the destination server, which then selects the highest
strength common cipher as part of the SSL handshake. The selected cipher is
then used to encrypt the data as it is sent over the secure channel.
HTTP Host Header:
An HTTP 1.1 client must send a
Host header in all HTTP 1.1 requests. The
Host header identifies the hostname and port number
of the requested resource as specified in the original URL given by the
client.
When routing messages on to target Web Services, the Enterprise Gateway can
forward on the Host as received from the client,
or it can specify the address and port number of the destination Web
Service in the Host header that it routes onwards.
Select Use Host header specified by client to force
the Enterprise Gateway to always forward on the original
Host header that it received from the client.
Alternatively, to configure the Enterprise Gateway to include the address and
port number of the destination Web Service in the
Host header, select the
Generate new Host header radio button.
|