Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Optimize Citrix ADC VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
Citrix应用ADC VPX配置在第一个boot of the Citrix ADC appliance in cloud
Install a Citrix ADC VPX instance on VMware ESX
Configuring Citrix ADC Virtual Appliances to use VMXNET3 Network Interface
Migrating the Citrix ADC VPX from E1000 to SR-IOV or VMXNET3 Network Interfaces
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
Citrix应用ADC VPX配置在第一个boot of the Citrix ADC appliance on VMware ESX hypervisor
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
配置高可用性与多个设置IP addresses and NICs by using PowerShell commands
Configure a Citrix ADC VPX instance to use Azure accelerated networking
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
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
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
-
gRPC with Responder Policy Configuration
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
Configuring CloudBridge Connector between Datacenter and AWS Cloud
配置一个CloudBridge连接器之间的隧道a Citrix ADC Appliance and Virtual Private Gateway on AWS
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
配置一个CloudBridge连接器之间的隧道a Citrix ADC Appliance and Cisco IOS Device
配置一个CloudBridge连接器之间的隧道a Citrix ADC Appliance and Fortinet FortiGate Appliance
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!
gRPC with the responder policy
The gRPC with responder policy configuration explains how a Citrix ADC appliance provides different responses to gRPC requests over the HTTP/2 protocol. When users request a website home page, you might want to provide a different home page depending on where each user is located or the browser the user is using.
The following diagram shows the components that interact.
- Enable the responder feature on the appliance.
- Configure the responder action to generate a custom response, redirect a request to a different webpage, or reset a connection.
- Configure the responder policy for determining the gRPC requests (traffic) on which an action has to be taken.
- Bind the responder policy to the load balancing virtual server to examine if the traffic matches the policy expression.
- By using a responder policy, you can perform the following based on the gRPC status code.
Configure gRPC call termination with the responder policy by using the CLI
配置gRPC调用终止与响应der policy, you must complete the following steps:
- Enable the responder feature
- Add a responder action
- Add a responder policy and associate responder action
- Bind the responder policy to load balancing virtual server
Enable the responder feature
To use the responder feature, you must first enable it.
At the command prompt, type:
enable ns responder
Add the responder action
After enabling the feature, you must configure the responder action for handling the gRPC response based on the status code returned by the back-end server.
At the command prompt, type:
add responder action
Example:
add responder action grpc-act respondwith "HTTP/1.1 200 OK\r\nServer: NS-Responder\r\nContent-Type:application/grpc\r\ngrpc-status: 12\r\ngrpc-message: Not Implemented\r\n\r\n" + "Method: " + HTTP.REQ.URL+ "is not implemented."
Adding responder policy
After you configure a responder action, you must next configure a responder policy to select the gRPC request to which the Citrix ADC appliance must respond.
At the command prompt, type:
add responder policy
Example:
add responder policy grpc-resp-pol1 HTTP.REQ.URL.NE(“/helloworld.Greeter/SayHello”) grpc-act
Bind responder policy to load balancing virtual server
To put a policy into effect, you must bind it to the load balancing virtual server with the gRPC service.
At the command prompt, type:
bind responder global
Example:
绑定磅vserver lb-grpc svc-grpc -policyName grpc -resp-pol1 –priority 100
For more information about the responder policy, seeResponder Policytopic.
策略表达式匹配gRPC协议健壮er fields
The Citrix ADC appliance supports the following policy expressions in the gRPC configuration:
gRPC protocol buffer field access.The arbitrary gRPC API call matches the message field number with the new policy expressions. In a PI configuration, the matches are done using only the ‘field numbers’ and ‘API path’.
gRPC header filtering.The “HttpProfile” parameters for gRPC is used to adjust the default behavior of gRPC parsing (including gRPC policy expressions). The following parameters are applicable to gRPC policy expressions:
gRPCLengthDelimitation.It is enabled by default and expects the protocol buffers to be presented with a length delimited message.
gRPCHoldLimit.The default value is 131072. It is the maximum protocol buffer message size in bytes. It is also the maximum string length and the maximum ‘byte’ field length as well.
Configure gRPC advance policy expressions by using the CLI
At the command prompt, type:
set ns httpProfile -http2 ( ENABLED | DISABLED ) -gRPCLengthDelimitation ( ENABLED | DISABLED ) -gRPCHoldLimit
Example:
set ns httpProfile http2gRPC -http2 ENABLED -gRPCLengthDelimitation ENABLED -gRPCHoldLimit 131072
Configure gRPC header filtering parameters by using the GUI
Navigate toSystem > Profilesand clickHTTP Profiles.
On theCreate HTTP Profilepage, scroll down toHTTP/3section, selectgRPC Length Delimitation.
The following policy expression example shows a value in message 5, submessage 4, and field 3. It is a 32-bit int equal to 2.
http.req.body(1000).grpc.message(5).message(4).int32(3).eq(2)
The following policy expressions are added for matching gRPC protocol buffer message fields by number:
- message
- double
- float
- int32
- int64
- uint32
- uint64
- sint64
- sint32
- fixed32
- fixed64
- sfixed32
- sfixed64
- bool
- string
- enum
- bytes
API path matching
The API path matching is used to match the correct gRPC API call when more than one API is used. Match the API path, which can be found in the ‘: path’ pseudo header in the HTTP request.
Example:
http.req.header(":path").eq("acme.inventory.v1/ListBooks")
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.