-
Getting Started with Citrix NetScaler
-
Deploy a Citrix NetScaler VPX instance
-
Install a Citrix 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
-
-
Deploying NetScaler VPX Instances on AWS
-
Upgrade and downgrade a NetScaler appliance
-
-
-
-
-
-
Overriding Static Proximity Behavior by Configuring Preferred Locations
-
Example of a Complete Parent-Child Configuration Using the Metrics Exchange Protocol
-
Configuring Global Server Load Balancing for DNS Queries with NAPTR records
-
Using the EDNS0 Client Subnet Option for Global Server Load Balancing
-
-
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
-
Use source IP address of the client when connecting to the server
-
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 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
Front End Optimization
-
-
-
-
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Front end optimization
Note: Front end optimization is available if you have an Advanced or Premium Citrix ADC license and are running Citrix ADC release 10.5 or later.
The HTTP protocols that underlie web applications were originally developed to support transmission and rendering of simple web pages. New technologies such as JavaScript and cascading style sheets (CSS), and new media types such as Flash videos and graphics-rich images, place heavy demands on front-end performance, that is, on performance at the browser level.
The Citrix ADC front end optimization (FEO) feature addresses such issues and reduces the load time and render time of web pages by:
- Reducing the number of requests.
- Required for rendering each page.
- Reducing the number of bytes in page responses.
Simplifying and optimizing the content served to the client browser.
You can customize your FEO configuration to provide the best results for your users. Citrix ADCs support numerous web content optimizations for both desktop and mobile users. The following tables describe the front-end optimizations provided by the FEO feature, and the operations performed on different types of files.
Optimizations performed by the FEO feature
Web Optimization | Problem | What Citrix ADC FEO feature does | Benefits |
---|---|---|---|
Inlining | Client browsers often send multiple requests to servers for loading external CSS, images, and JavaScript associated with the web page. | CSS inline, JavaScript inline, CSS combine | Loading the external CSS, images, and JavaScript inline with the HTML files improves page-rendering time. This optimization is beneficial for content that will be viewed only once, and for mobile devices that have limited cache sizes. |
Minification | Data fetched from servers includes inessential characters such as white spaces, comments, and newline characters. The time that browsers spend in processing such data creates website latency. | CSS minification, JavaScript minification, Removal of HTML comments | Minified files consume less bandwidth and avoid the latency caused by special processing. |
Image optimization | Mobile browsers often have slow connection speeds and limited cache memory. Downloading images on mobile clients consumes more bandwidth, processing time, and cache space, resulting in web site latency. | JPEG optimization, CSS image inlining, Image shrink-to attributes, GIF to PNG conversion, HTML image inlining, WebP image conversion, JPEG, GIF, PNG to JPEG-XR image conversion | Reduces the image to the size indicated in image tag by Citrix ADC, enabling client browsers to load images faster. |
Repositioning | Inefficient processing of external CSS, images, and JavaScript increases page-load time. | Image lazy loading, CSS move to Head, JavaScript move to end | Repositions HTML elements, to reduce rendering time for web pages and enable client browsers to load the objects faster. |
Connection Management | Many browsers set limits on the number of simultaneous connections that can be established to a single domain. This can cause browsers to download webpage resources one at a time, resulting in higher browsers time. | Domain sharding | Overcomes the connection limitation, which improves page-rendering time by enabling client browsers to download more resources in parallel. |
Web Optimizations performed on different file types:
Citrix ADC can perform web optimizations on CSS, images, Javascript, and HTML. For more information, see Web Optimizations pdf.
Note: The front end optimization feature supports ASCII characters only. It does not support the unicode character set.
How front end optimization works
After the Citrix ADC receives the response from the server:
-
Parses the contents of the page, creates an entry in the cache (wherever applicable), and applies the FEO policy.
For example, a Citrix ADC can apply the following optimization rules:
- Remove white spaces or comments present within a CSS or JavaScript.
- Combine one or more CSS files to one file.
- Convert GIF image format to PNG format.
- Rewrites the embedded objects and saves the optimized content in the cache, with a different signature than the one used for the initial cache entry.
- For subsequent requests, fetches the optimized objects from the cache, not from the server, and forwards the responses to the client.
Remove extraneous information such as white spaces and comments.
** Remove extraneous information such as white spaces and comments.
The period during which the browser can use the cached resource without checking to see if fresh content is available on the server.
Configure front end optimization
Optionally, you can change the values of the front end optimization global settings. Otherwise, begin by creating actions that specify the optimization rules to be applied to the embedded objects.
After configuring actions, create policies, each with a rule specifying a type of request for which to optimize the response, and associate the actions with the policies.
Note: The Citrix ADC evaluates front end optimization policies at request time only, not at response time.
To put the policies into effect, bind them to bind points. You can bind a policy globally, so that it applies to all traffic that flows through the Citrix ADC, or you can bind the policy to a load balancing or content switching virtual server of type HTTP or SSL. When you bind a policy, assign it a priority. A lower priority number indicates a higher value. The Citrix ADC applies the policies in the order of their priorities.
Prerequisites
Front end optimization requires the Citrix ADC integrated caching feature to be enabled. Additionally, you must perform the following integrated caching configurations:
- Allocate cache memory.
- Set the maximum response size and memory limit for a default cache content group.
For more information on configuring integrated caching, see Integrated Caching.
Note: The term Integrated Cache can be interchangeably used with AppCache; note that from a functionality point of view, both terms mean the same.
To configure front end optimization by using the command line interface
At the command prompt, do the following:
- Enable the front end optimization feature.
enable ns feature FEO
- Create one or more front end optimization actions.
add feo action <name> [-imgShrinkToAttrib] [-imgGifToPng] ...
Example: To add a front end optimization action for converting images in GIF format to PNG format and to extend cache expiry period:
add feo action allact -imgGifToPng -pageExtendCache
- [Optional] Specify non-default values for front end optimization global settings.
set feo parameter [-cacheMaxage <integer>] [-JpegQualityPercent <integer>] [-cssInlineThresSize <integer>] [-inlineJsThresSize <integer> [-inlineImgThresSize <integer>]
Example: To specify the cache maximum expiry period:
set feo parameter -cacheMaxage 10
- Create one or more front end optimization policy.
add feo policy <name> <rule> <action>
Example: To add a front end optimization policy and associate it with the above specifiedallact action:
`>add feo policy pol1 TRUE allact
add feo policy pol1 “(HTTP.REQ.URL.CONTAINS("testsite"))” allact1`
5. Bind the policy to a load balancing or content switching virtual server, or bind it globally.
bind lb vserver <name> -policyName <string> -priority <num>
bind cs vserver <name> -policyName <string> -priority <num>
bind feo global <policyName> <priority> -type <type> <gotoPriorityExpression>
Example: To apply the front end optimization policy to a virtual server named “abc”:
> bind lb vserver abc -policyName pol1 -priority 1 -type NONE
Example: To apply the front end optimization policy for all the traffic reaching the ADC:
> bind feo global pol1 100 -type REQ_DEFAULT
- Save the configuration. save ns config
Configure front end optimization by using the GUI
- Navigate to Optimization > Front End Optimization > Actions, click Add and create a front end optimization action by specifying the relevant details.
- [Optional] Specify the front end optimization global settings.
- Navigate to Optimization > Front End Optimization, and on the right-pane, under Settings, click Change Front End Optimization settings and specify the front end optimization global settings.
- Create a front end optimization policy.
- Navigate to Optimization > Front End Optimization > Policies, click Add and create a front end optimization policy by specifying the relevant details.
- Bind the policy to a load balancing or content switching virtual server.
- Navigate to Optimization > Front End ptimization > Policies.
- Select a front end optimization policy and click Policy Manager.
- Under Front End Optimzation Policy Manager, bind the front end optimization policy to a load balancing or content switching virtual server.
Verify front end optimization configuration
The dashboard utility displays summary and detailed statistics in tabular and graphic formats. You can view the FEO statistics to evaluate your FEO configuration.
Optionally, you can also display statistics for an FEO policy, including the number of hits that the policy counter increments during policy based FEO.
Note For more information about statistics and charts, see the Dashboard help on the Citrix ADC appliance.
View FEO statistics by using the command line interface
At the command prompt, type the following commands to display a summary of FEO statistics, FEO policy hits and details, and detailed FEO statistics, respectively:
-
stat feo
Note: The stat feo policy command displays statistics only for advanced FEO policies. show feo policy name
stat feo -detail
View FEO statistics on Citrix ADC dashboard
In the dashboard GUI, you can:
- Select Front End Optimization to display a summary of FEO statistics.
- Click the Graphical View tab to display the rate of requests processed by the FEO feature.
Sample optimization:
Refer to the Sample pdf for some examples of content optimization actions that are applied on HTML content and the embedded objects within the HTML content.
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.