Dell 3-DNS Especificaciones descargar pdf (Pagina 180)

Chapter 4: Configuring the High-Level Network

4-100

• A header in which the session ID is the current session ID. The proper

format of this header is SSLClientCurrentSessionID:X, where X

represents the current SSL session ID.

If you enable the insertion of session ID headers, but specify neither of these

two types of session IDs, the SSL proxy inserts the session ID initially

negotiated with the client.

To insert a session ID header using the Configuration utility

1. In the navigation pane, click Proxies.

2. Click the Add button.

3. In the Insert Client Session ID box, check either or both of the

Initial and Current check boxes.

4. Click Done.

To insert a session ID header from the command line

To insert a session ID header into an HTTP request using the command line,

specify the sessionid insert argument with the bigpipe proxy command, as

follows:

b proxy <ip>:<service> [clientssl] sessionid insert [initial] [current] [enable]

Note

One use of client session IDs is to enable SSL persistence. Note that SSL

persistence should not be enabled on pools that load balance plain-text

traffic, that is, traffic resulting from SSL proxies on which SSL termination

is enabled.

Specifying SSL ciphers and protocol versions

For each SSL proxy, you can specify both the ciphers available for SSL

connections, and the protocol versions that are not allowed.

When configuring ciphers and protocol versions, you must ensure that the

ciphers and the protocol versions configured for the SSL proxy match those

of the proxy’s peer. That is, ciphers and protocol versions for the client-side

SSL proxy must match those of the client, and ciphers and protocol versions

for the server-side SSL proxy must match those of the server.

For example,

a client might connect to and successfully establish an SSL

connection to an SSL proxy that is configured to use both client-side and

server-side SSL. After the client sends additional data (such as an HTTP

request), the SSL proxy attempts to establish an SSL connection to a server.

However, the SSL proxy might be configured to enable only 3DES ciphers

for server-side SSL, and the servers might be configured to accept only RC4

ciphers. In this case, the SSL handshake between the SSL proxy and the

server will fail because there are no common ciphers enabled. This results in

1 2 ... 175 176 177 178 179 180 181 182 183 184 185 ... 425 426

Sin comentarios

Dell 3-DNS Especificaciones Pagina 180