- Configuring SSL Offloading
- Managing Certificates
- Managing Certificate Revocation Lists
- Monitoring Certificate Status with OCSP
- Configuring Client Authentication
- Customizing the SSL Configuration
- Configuring SSL Actions and Policies
- Use Case 1: Configuring SSL Offloading with End-to-End Encryption
- Use Case 2: Configuring Transparent SSL Acceleration
- Use Case 3: Configuring SSL Acceleration with HTTP on the Front End and SSL on the Back End
- Use Case 4: SSL Offloading with Other TCP Protocols
- Use Case 5: Configuring SSL Bridging
- Use Case 6: Configuring SSL Monitoring when Client Authentication is Enabled on the Backend Service
- Use Case 7: Configuring a Secure Content Switching Server
- Ciphers Supported by the NetScaler Appliance
- Cipher/Protocol Support Matrix on the NetScaler Appliance
- FIPS
- Support for Thales nShield® HSM
- Troubleshooting
- SSL FAQs
Use Case 7: Configuring a Secure Content Switching Server
May 26, 2015
An SSL-based content switching virtual server first decrypts the secure data and then redirects the data to appropriately configured servers as determined by the type of content and the configured content switching policies. The packets sent to the server have a mapped IP address as the source IP address.
The following example shows the steps to configure two address-based virtual servers to perform load balancing on the HTTP services. One virtual server, Vserver-LB-HTML, load balances the dynamic content (cgi, asp), and the other, Vserver-LB-Image, load balances the static content (gif, jpeg). The load-balancing method used is the default, LEASTCONNECTION. A content switching SSL virtual server, Vserver-CS-SSL, is then configured to perform SSL acceleration and switching of HTTPS requests on the basis of configured content switching policies.
Example
> enable ns feature lb cs ssl > add lb vserver Vserver-LB-HTML http 10.1.1.2 80 > add lb vserver Vserver-LB-Image http 10.1.1.3 80 > add service s1 10.1.1.4 http 80 > add service s2 10.1.1.5 http 80 > add service s3 10.1.1.6 http 80 > add service s4 10.1.1.7 http 80 > bind lb vserver Vserver-LB-HTML s1 > bind lb vserver Vserver-LB-HTML s2 > bind lb vserver Vserver-LB-Image s3 > bind lb vserver Vserver-LB-Image s4 > add cs vserver Vserver-CS-SSL ssl 10.1.1.1 443 > add cs policy pol1 -url "*.cgi" > add cs policy pol2 -url "*.asp" > add cs policy pol3 -url "*.gif" > add cs policy pol4 -url "*.jpeg" > bind cs vserver Vserver-CS-SSL -policyName pol1 Vserver-LB-HTML > bind cs vserver Vserver-CS-SSL -policyName pol2 Vserver-LB-HTML > bind cs vserver Vserver-CS-SSL -policyName pol3 Vserver-LB-Image > bind cs vserver Vserver-CS-SSL -policyName pol4 Vserver-LB-Image > add certkey mykey -cert /nsconfig/ssl/ns-root.cert -key /nsconfig/ssl/ns-root.key > bind certkey Vserver-CS-SSL mykey > > show cs vserver Vserver-CS-SSL Vserver-CS-SSL (10.1.1.1:443) - SSL Type: CONTENT State: UP Last state change was at Tue Jul 13 02:11:37 2010 Time since last state change: 0 days, 00:02:12.440 Client Idle Timeout: 180 sec Down state flush: ENABLED Disable Primary Vserver On Down : DISABLED State Update: DISABLED Default: Content Precedence: RULE Vserver IP and Port insertion: OFF Case Sensitivity: ON Push: DISABLED Push VServer: Push Label Rule: none