-
-
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
-
-
Configuring and Binding a Traffic Rate Policy
-
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!
Configuring and binding a traffic rate policy
You implement rate-based application behavior by configuring a policy in an appropriate NetScaler feature. The feature must support Advanced policies. The policy expression must contain the following expression prefix to enable the feature to analyze the traffic rate:
sys.check_limit(<limit_identifier>)
<!--NeedCopy-->
Where limit_identifier is the name of a limit identifier.
The policy expression must be a compound expression that contains at least two components:
- An expression that identifies traffic to which the rate limit identifier is applied. For example:
http.req.url.contains("my_aspx.aspx").
<!--NeedCopy-->
- An expression that identifies a rate limit identifier, for example, sys.check_limit(“my_limit_identifier”). This must be the last expression in the policy expression.
To configure a rate-based policy by using the command line interface
At the command prompt, type the following command to configure a rate-based policy and verify the configuration:
add cache|dns|rewrite|responder policy <policy_name> -rule expression && sys.check_limit("<LimitIdentifierName>") [<feature-specific information>]
<!--NeedCopy-->
Following is a complete example of a rate-based policy rule. Note that this example assumes that you have configured the responder action, send_direct_url, that is associated with the policy. Note that the sys.check_limit parameter must be the last element of the policy expression:
add responder policy responder_threshold_policy "http.req.url.contains("myindex.html") && sys.check_limit("my_limit_identifier")" send_direct_url
<!--NeedCopy-->
For information about binding a policy globally or to a virtual server, see “Binding Advanced policy Policies.”
To configure a rate-based policy by using the configuration utility
-
In the navigation pane, expand the feature in which you want to configure a policy (for example, Integrated Caching, Rewrite, or Responder), and then click Policies.
-
In the details pane, click Add. In Name, enter a unique name for the policy.
-
Under Expression, enter the policy rule, and make sure that you include the sys.check_limit parameter as the final component of the expression. For example:
http.req.url.contains("my_aspx.aspx") && sys.check_limit("my_limit_identifier") <!--NeedCopy-->
-
Enter feature-specific information about the policy.
For example, you may be required to associate the policy with an action or a profile. For more information, see the feature-specific documentation.
-
Click Create, and then click Close.
-
Click Save.
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.