Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Optimize Citrix ADC VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
Apply Citrix ADC VPX configurations at the first boot of the Citrix ADC appliance in cloud
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
Install a Citrix ADC VPX instance on Linux-KVM platform
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
Deploy a Citrix ADC 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
Configure a Citrix ADC VPX instance to use SR-IOV network interface
Configure a Citrix ADC VPX instance to use Enhanced Networking with AWS ENA
Deploy a Citrix ADC VPX instance on Microsoft Azure
Network architecture for Citrix ADC VPX instances on Microsoft Azure
Configure multiple IP addresses for a Citrix ADC 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
Configure a Citrix ADC VPX instance to use Azure accelerated networking
配置HA-INC节点使用Citrix高availability template for internet-facing applications
Configure a high-availability setup with Azure external and internal load balancers simultaneously
Configure address pools (IIP) for a Citrix Gateway appliance
Upgrade and downgrade a Citrix ADC appliance
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
On-premises Citrix 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 for load balancing
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
Use case 15: Configure layer 4 load balancing on the Citrix ADC appliance
-
-
-
Authentication and authorization for System Users
HTTP Configurations
-
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 Citrix ADC 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!
HTTP configurations
Important:
Starting from Citrix ADC release 13.0 build 71.x, a Citrix ADC appliance can handle large header size HTTP requests to accommodate the L7 application requests. The header size can be configurable up to 120 KB.
HTTP configurations for a Citrix ADC appliance can be specified in an entity called an HTTP profile, which is a collection of HTTP settings. The HTTP profile can then be associated with services or virtual servers that want to use these HTTP configurations.
A default HTTP profile can be configured to set the HTTP configurations that is applied by default, globally to all services and virtual servers.
Note:
When an HTTP parameter has different values for service, virtual server, and globally, the value of the most-specific entity (the service) is given the highest precedence.
The Citrix ADC appliance also provides other approaches for configuring HTTP. Read on for more information.
The Citrix ADC supports a WebSocket protocol which allows browsers and other clients to create a bi-directional, full duplex TCP connection to the servers. The Citrix ADC implementation of WebSocket is RFC6455compliant.
Note:
A Citrix ADC appliance now supports the User Source IP (USIP) address configuration for both HTTP/1.1 and HTTP/2 protocols.
Setting global HTTP parameters
The Citrix ADC appliance allows you to specify values for HTTP parameters that are applicable to all Citrix ADC services and virtual servers. This can be done using:
- Default HTTP profile
- Global HTTP command
Default HTTP profile
An HTTP profile, named as nshttp_default_profile, is used to specify HTTP configurations that is used if no HTTP configurations are provided at the service or virtual server level.
Notes:
Not all HTTP parameters can be configured through the default HTTP profile. Some settings are performed by using the global HTTP command (see the following section).
The default profile does not have to be explicitly bound to a service or virtual server.
To configure the default HTTP profile
Using the command line interface, at the command prompt enter:
set ns httpProfile nshttp_default_profile …
On the GUI, navigate toSystem>Profiles, clickHTTP Profilesand update nshttp_default_profile.
Global HTTP command
Another approach you can use to configure global HTTP parameters is the global HTTP command. In addition to some unique parameters, this command duplicates some parameters that can be set by using an HTTP profile. Any update made to these duplicate parameters is reflected in the corresponding parameter in the default HTTP profile.
For example, if the maxReusePool parameter is updated using this approach, the value is reflected in the maxReusePool parameter of the default HTTP profile (nshttp_default_profile).
Note:
Citrix recommends that you use this approach only for HTTP parameters that are not available in the default HTTP profile.
To configure the global HTTP command
Using the command line interface, at the command prompt enter:
set ns httpParam …
On the GUI, navigate toSystem > Settings, clickChange HTTP parametersand update the required HTTP parameters.
To configure an ignore Coding scheme for connect request
To enable HTTP/2 and set HTTP/2 parameters to ignore the Coding scheme in the connect request, at the command prompt, type:
set ns httpParam [-ignoreConnectCodingScheme ( ENABLED | DISABLED )]
Example:
set ns httpParam -ignoreConnectCodingScheme ENABLED
To bind the HTTP profile to a virtual server by using the Citrix ADC command line
Configure HTTP profile to drop TRACE or TRACK invalid requests
You can enable the markTraceReqInval parameter to mark TRACK and TRACK requests as invalid. When you enable this option along with the dropInvalidReqs option on the virtual IP address, you can reset a client sending TRACE or TRACK requests to a Citrix ADC appliance.
配置HTTP配置文件使用CLI
At the command prompt, type:
set ns httpProfile
Example:
set ns httpProfile profile1 -markTraceReqInval ENABLED
Configure HTTP profile for a service group
At the command prompt, type:
add serviceGroup @ [-cacheType ] [-td ] [-maxClient ] [-maxReq ] [-cacheable ( YES | NO )] [-cip ( ENABLED | DISABLED ) []] [-usip ( YES | NO )] [-pathMonitor ( YES | NO )] [-pathMonitorIndv ( YES | NO )] [-useproxyport ( YES | NO )] [-healthMonitor ( YES | NO )] [-sp ( ON | OFF )] [-rtspSessionidRemap ( ON | OFF )] [-cltTimeout ] [-svrTimeout ] [-CKA ( YES | NO )] [-TCPB ( YES | NO )] [-CMP ( YES | NO )] [-maxBandwidth ] [-monThreshold ] [-state ENABLED DISABLED )][-downStateFlush ( ENABLED | DISABLED )] [-tcpProfileName ] [-httpProfileName ] [-comment ] [-appflowLog ( ENABLED | DISABLED )] [-netProfile ] [-autoScale -memberPort [-autoDisablegraceful ( YES | NO )] [-autoDisabledelay ] ] [-monConnectionClose ( RESET | FIN )]
Example:
add serviceGroup Service-Group-1 HTTP -maxClient 0 -maxReq 0 -cip ENABLED -usip NO -useproxyport YES -cltTimeout 200 -svrTimeout 300 -CKA NO -TCPB NO -CMP NO -httpProfileName profile1
Configure the HTTP profile using the Citrix ADC GUI
To mark TRACE or TRACK invalid requests, complete the following procedure.
- Sign into Citrix ADC appliance and navigate toConfiguration>System>Profiles.
- In theHTTP Profilestab page, clickAdd.
- In theCreate HTTP Profilepage, selectMark TRACE Requests as Invalidoption.
ClickCreate.
Setting service or virtual server specific HTTP parameters
使用HTTP概要,您可以指定HTTP参数rs for services and virtual servers. You have to define an HTTP profile (or use a built-in HTTP profile) and associate the profile with the appropriate service and virtual server.
Note:
您还可以修改默认的HTTP参数profiles as per your requirements.
To specify service or virtual server level HTTP configurations by using the command line interface
At the command prompt, perform the following:
Configure the HTTP profile.
set ns httpProfile
... Bind the HTTP profile to the service or virtual server.
To bind the HTTP profile to the service:
set service
Example:
> set service service1 -httpProfileName profile1
To bind the HTTP profile to the virtual server:
set lb vserver
Example:
> set lb vserver lbvserver1 -httpProfileName profile1
To specify service or virtual server level HTTP configurations by using the GUI
At the GUI, perform the following:
Configure the HTTP profile.
Navigate toSystem>Profiles>HTTP Profiles, and create the HTTP profile.
Bind the HTTP profile to the service or virtual server.
Navigate toTraffic Management>Load Balancing>Services/Virtual Servers, and create the HTTP profile, which must be bound to the service/virtual server.
Built-in HTTP profiles
For convenience of configuration, the Citrix ADC provides some built-in HTTP profiles. Review the profiles listed and use it as it is or modify it to meet your requirements. You can bind these profiles to the required services or virtual servers.
Built-in profile | Description |
---|---|
nshttp_default_profile | Represents the default global HTTP settings on the appliance. |
nshttp_default_strict_validation | Settings for deployments that require strict validation of HTTP requests and responses. |
Sample HTTP configurations
Sample command line interface examples to configure the following:
- HTTP band statistics
- WebSocket connections
HTTP band statistics
Specify the band size for HTTP requests and responses.
> set protocol httpBand reqBandSize 300 respBandSize 2048 Done > show protocol httpband -type REQUEST
WebSocket connections
Enable WebSocket on the required HTTP profile.
> set ns httpProfile http_profile1 -webSocket ENABLED Done > set lb vserver lbvserver1 -httpProfileName profile1 Done
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix 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 Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.