HTTPS deployment scenarios

Configuring the HTTPS service

HTTPS service can be configured to manage inbound and outbound SSL contexts in forward proxy and reverse proxy environments. The following scenarios provide examples of settings for a variety of HTTPS deployments.

Web acceleration

The following two examples illustrate the appliance deployed as a reverse proxy, or Web accelerator. In a Web accelerated environment, secure traffic is offloaded from the Web server to the appliance.

Web acceleration example 1

The accelerated environment supports HTTPS traffic between the client and the cache, and HTTPS traffic between the cache and the origin server.

The following SSL context parameters are assumed:

SSL context

(Setup tab > Authentication > SSL Contexts)

Inbound context name = inctx

Outbound context name = outctx

Appliance name = ncache.com

Accelerated server name = server.com

Accelerated server IP address = 10.24.155.13

The following HTTPS parameter settings are required:

HTTPS

(Setup tab > HTTPS > General)

HTTPS = enabled

HTTPS inbound context acl = context "inctx" cache-port 443

HTTPS outbound context acl = context "outctx" server-port 443 and server-ip 10.24.155.13

Acceleration rule

(Setup tab > HTTPS > Web Server Acceleration)

HTTPS Web acceleration = enabled

HTTPS acceleration rule = * 443 ncache.com * 10.24.155.13 443 server.com *

Web acceleration example 2

The accelerated environment supports HTTPS traffic between the client and the cache, and HTTP traffic between the cache and the origin server.

The following SSL context parameters are assumed:

SSL context

(Setup tab > Authentication > SSL Contexts)

Inbound context name = inctx

Outbound context name = outctx

Appliance name = ncache.com

Accelerated server name = server.com

Accelerated server IP address = 10.24.155.13

The following HTTPS parameter settings are required:

HTTPS

(Setup tab > HTTPS > General)

HTTPS = enabled

HTTPS inbound context acl = context "inctx" cache-port 443

Acceleration rule

(Setup tab > HTTPS > Web Server Acceleration)

HTTPS Web acceleration = enabled

HTTPS acceleration rule = * 443 ncache.com * 10.24.155.13 80 server.com *

Forward proxy

The following example illustrates the appliance deployed as a forward proxy. In a forward proxy environment, the appliance handles requests from client Web browsers to an origin server.

Forward proxy example

In an HTTPS forward proxy configuration, client browsers use HTTPS to communicate with the appliance, and the appliance uses HTTPS to communicate with the origin server.

The following SSL context parameters are assumed:

SSL context

(Setup tab > Authentication > SSL Contexts)

Inbound context name = inctx

Outbound context name = outctx

Web server name = server.com

Web IP address = 10.24.155.13

The following HTTPS parameter settings are required:

HTTPS

(Setup tab > HTTPS > General)

HTTPS = enabled

HTTPS inbound context acl = context "inctx" server-port 443 and server-ip 10.24.155.13

HTTPS outbound context acl = context "outctx" server-port 443 and server-ip 10.24.155.13