-
Getting Started with NetScaler
-
Deploy a NetScaler VPX instance
-
Optimize NetScaler VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Apply NetScaler VPX configurations at the first boot of the NetScaler appliance in cloud
-
Configure simultaneous multithreading for NetScaler VPX on public clouds
-
Install a NetScaler VPX instance on Microsoft Hyper-V servers
-
Install a NetScaler VPX instance on Linux-KVM platform
-
Prerequisites for installing NetScaler VPX virtual appliances on Linux-KVM platform
-
Provisioning the NetScaler virtual appliance by using OpenStack
-
Provisioning the NetScaler virtual appliance by using the Virtual Machine Manager
-
Configuring NetScaler virtual appliances to use SR-IOV network interface
-
Configuring NetScaler virtual appliances to use PCI Passthrough network interface
-
Provisioning the NetScaler virtual appliance by using the virsh Program
-
Provisioning the NetScaler virtual appliance with SR-IOV on OpenStack
-
Configuring a NetScaler VPX instance on KVM to use OVS DPDK-Based host interfaces
-
-
Deploy a NetScaler VPX instance on AWS
-
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
-
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
-
Protect AWS API Gateway using the NetScaler Web Application Firewall
-
Configure a NetScaler VPX instance to use SR-IOV network interface
-
Configure a NetScaler VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Network architecture for NetScaler VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a NetScaler VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Deploy a NetScaler high-availability pair on Azure with ALB in the floating IP-disabled mode
-
Configure a NetScaler VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the NetScaler high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure a NetScaler VPX standalone instance on Azure VMware solution
-
Configure a NetScaler VPX high availability setup on Azure VMware solution
-
Configure address pools (IIP) for a NetScaler Gateway appliance
-
Deploy a NetScaler VPX instance on Google Cloud Platform
-
Deploy a VPX high-availability pair on Google Cloud Platform
-
Deploy a VPX high-availability pair with external static IP address on Google Cloud Platform
-
Deploy a single NIC VPX high-availability pair with private IP address on Google Cloud Platform
-
Deploy a VPX high-availability pair with private IP addresses on Google Cloud Platform
-
Install a NetScaler VPX instance on Google Cloud VMware Engine
-
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
-
-
-
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
-
Authentication and authorization for System Users
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Rewrite ports and protocols for HTTP redirection
Virtual servers and the services that are bound to them might use different ports. When a service responds to an HTTP connection with a redirect, you might need to configure the NetScaler appliance to modify the port and the protocol to make sure that the redirection goes through successfully. You do this by enabling and configuring the redirectPortRewrite setting.
This setting affects only HTTP and HTTPS traffic. If this setting is enabled on a virtual server, the virtual server rewrites the port on redirects, replacing the port used by the service with the port used by the virtual server.
If the virtual server or service is of type SSL, you must enable SSL redirect on the virtual server or service. If both the virtual server and service are of type SSL, enable SSL redirect on the virtual server.
The redirectPortRewrite setting can be used in the following scenarios:
- The virtual server is of type HTTP and the services are of type SSL.
- The virtual server is of type SSL and the services are of type HTTP.
- The virtual server is of type HTTP and the services are of type HTTP.
- The virtual server is of type SSL and the services are of type SSL.
Scenario 1: The virtual server is of type HTTP and services are of type SSL. SSL redirect, and optionally port rewrite, is enabled on the service. If port rewrite is enabled, the port of HTTPS URLs is rewritten. HTTP URLs from the server are sent as is to the client.
Only SSL redirect is enabled. The virtual server can be configured on any port. See the following table:
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
http://domain.com / |
http://domain.com:8080 / |
http://domain.com:8080 / |
https://domain.com / |
https://domain.com / |
https://domain.com:444 / |
https://domain.com:444 / |
SSL redirect and port rewrite are enabled. The virtual server is configured on port 80. See the following table:
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
http://domain.com / |
http://domain.com:8080 / |
http://domain.com:8080 / |
https://domain.com / |
https://domain.com / |
https://domain.com:444 / |
https://domain.com / |
SSL redirect and port rewrite are enabled. Virtual server is configured on port 8080. See the following table:
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
http://domain.com / |
http://domain.com:8080 / |
http://domain.com:8080 / |
https://domain.com / |
http://domain.com:8080 / |
https://domain.com:444 / |
http://domain.com:8080 / |
Scenario 2: The virtual server is of type SSL and services are of type HTTP. If port rewrite is enabled, only the port of HTTP URLs is rewritten. HTTPS URLs from the server are sent as is to the client.
SSL redirect is enabled on the virtual server. The virtual server can be configured on any port. See the following table.
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
https://domain.com / |
http://domain.com:8080 / |
https://domain.com:8080 / |
https://domain.com / |
https://domain.com / |
https://domain.com:444 / |
https://domain.com:444 / |
SSL redirect and port rewrite are enabled on the virtual server. The virtual server is configured on port 443. See the following table:
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
https://domain.com / |
http://domain.com:8080 / |
https://domain.com / |
https://domain.com / |
https://domain.com / |
https://domain.com:444 / |
https://domain.com:444 / |
SSL redirect and port rewrite are enabled. The virtual server is configured on port 444. See the following table:
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
https://domain.com:444 / |
http://domain.com:8080 / |
https://domain.com:444 / |
https://domain.com / |
https://domain.com / |
https://domain.com:445 / |
https://domain.com:445 / |
Scenario 3: The virtual server and service are of type HTTP. Port rewrite must be enabled on the virtual server. Only the port of HTTP URLs is rewritten. HTTPS URLs from the server are sent as is to the client.
The virtual server is configured on port 80. See the following table:
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
http://domain.com / |
http://domain.com:8080 / |
http://domain.com / |
https://domain.com / |
https://domain.com / |
https://domain.com:444 / |
https://domain.com:444 / |
The virtual server is configured on port 8080. See the following table:
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
http://domain.com:8080 / |
http://domain.com:8080 / |
http://domain.com:8080 / |
https://domain.com / |
https://domain.com / |
https://domain.com:445 / |
https://domain.com:445 / |
Scenario 4: The virtual server and service are of type SSL. If port rewrite is enabled, only the port of HTTPS URLs is rewritten. HTTP URLs from the server are sent as is to the client.
SSL redirect is enabled on the virtual server. The virtual server can be configured on any port. See the following table:
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
http://domain.com / |
http://domain.com:8080 / |
http://domain.com:8080 / |
https://domain.com / |
https://domain.com / |
https://domain.com:444 / |
https://domain.com:444 / |
SSL redirect and port rewrite are enabled on the virtual server. The virtual server is configured on port 443. See the following table:
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
http://domain.com / |
http://domain.com:8080 / |
http://domain.com:8080 / |
https://domain.com / |
https://domain.com / |
https://domain.com:444 / |
https://domain.com / |
SSL redirect and port rewrite are enabled on the virtual server. The virtual server is configured on port 444. See the following table:
Redirect URL from the Server | Redirect URL sent to the Client |
---|---|
http://domain.com / |
http://domain.com / |
http://domain.com:8080 / |
http://domain.com:8080 / |
https://domain.com / |
https://domain.com:444 / |
https://domain.com:445 / |
https://domain.com:444 / |
To configure HTTP redirection on a virtual server by using the CLI
At the command prompt, type:
set lb vserver <name> -redirectPortRewrite (ENABLED | DISABLED)
<!--NeedCopy-->
Example:
set lb vserver Vserver-LB-1 -redirectPortRewrite enabled
<!--NeedCopy-->
To configure HTTP redirection on a virtual server by using the GUI
- Navigate to Traffic Management > Load Balancing > Virtual Servers.
- Open the virtual server, and in the Advanced Settings pane, click Traffic Settings, and then select Rewrite.
To configure SSL Redirect on an SSL virtual server or service by using the CLI
At the command prompt, type:
set ssl vserver <vServerName> - sslRedirect (ENABLED | DISABLED)
set ssl service <serviceName> - sslRedirect (ENABLED | DISABLED)
<!--NeedCopy-->
Example:
set ssl vserver Vserver-SSL-1 -sslRedirect enabled
set ssl service service-SSL-1 -sslRedirect enabled
<!--NeedCopy-->
To configure SSL redirection and SSL port rewrite on an SSL virtual server or service by using the GUI
- Navigate to Traffic Management > Load Balancing > Virtual Servers, and open the virtual server.
- In Advanced Settings, click SSL Parameters, and select SSL Redirect.
Share
Share
In this article
- To configure HTTP redirection on a virtual server by using the CLI
- To configure HTTP redirection on a virtual server by using the GUI
- To configure SSL Redirect on an SSL virtual server or service by using the CLI
- To configure SSL redirection and SSL port rewrite on an SSL virtual server or service by using the GUI
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.