-
AppExpert Applications and Templates
-
Configure application authentication, authorization, and auditing
-
-
Introduction to Policies and expressions
-
Classic and Advanced Policy Expressions
-
Advanced Policy Expressions: Working with Dates, Times, and Numbers
-
Advanced Policy Expressions: Parsing HTTP, TCP, and UDP Data
-
Advanced Policy Expressions: IP and MAC Addresses, Throughput, VLAN IDs
-
-
-
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!
Classic and advanced policy expressions
One of the most fundamental components of a policy is its rule. A policy rule is a logical expression that enables the policy to analyze traffic. Most of the policy’s functionality is derived from its expression.
An expression matches characteristics of traffic or other data with one or more parameters and values. For example, an expression can enable the Citrix ADC to accomplish the following:
- Determine whether a request contains a certificate.
- Determine the IP address of a client that sent a TCP request.
- Identify the data that an HTTP request contains (for example, a popular spreadsheet or word processing application).
- Calculate the length of an HTTP request.
About classic expressions
Classic expressions enable you to evaluate basic characteristics of data. They have a structured syntax that performs string matching and other operations.
Following are a few simple examples of classic expressions:
- An HTTP response contains a particular type of Cache Control header.
res.http.header Cache-Control contains public
- An HTTP response contains image data.
res.http.header Content-Type contains image
- An SSL request contains a certificate.
req.ssl.client.cert exists
About advanced policy expressions
Any feature that uses default syntax policies also uses Advanced expressions. For information about which features use Advanced policies, see the table Citrix ADC Feature, Policy Type, and Policy Usage.
Advanced policy expressions have a few other uses. In addition to configuring Advanced expressions in policy rules, you configure Advanced expressions in the following situations:
-
Integrated Caching:
You use Advanced policy expressions to configure a selector for a content group in the integrated cache.
-
Load Balancing:
You use Advanced policy expressions to configure token extraction for a load balancing virtual server that uses the TOKEN method for load balancing.
-
Rewrite:
You use Advanced policy expressions to configure rewrite actions.
-
Rate-based policies:
You use Advanced policy expressions to configure limit selectors when configuring a policy to control the rate of traffic to various servers.
Following are a few simple examples of Advanced policy expressions:
- An HTTP request URL contains no more than 500 characters.
http.req.url.length \<= 500
- An HTTP request contains a cookie that has fewer than 500 characters.
http.req.cookie.length \< 500
- An HTTP request URL contains a particular text string.
http.req.url.contains(".html")
Share
Share
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.