-
-
Use Case: ESI support for fetching and updating content dynamically
-
-
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!
Use Case: ESI support for fetching and updating content dynamically
Edge Side Includes (ESI) is a markup language for edge-level dynamic Web content assembly. It helps in accelerating dynamic Web-based applications by defining a simple markup language to describe cacheable and non-cacheable Web page components that can be aggregated, assembled, and delivered at the network edge. By using HTTP callouts on the NetScaler appliance, you can read through the ESI constructs and aggregate or assemble content dynamically.
To implement this configuration, you must perform the following tasks:
- Enable rewrite on the NetScaler appliance.
- Create an HTTP callout on the appliance and configure it with details about the external server and other required parameters.
- Configure a rewrite action to replace the ESI content with the callout response body.
- Configure a rewrite policy to specify the conditions under which the action is performed, and then bind the rewrite policy globally.
Enabling rewrite
Rewrite must be enabled before it is used on the NetScaler appliance. The following procedure describes the steps to enable the rewrite feature.
To enable rewrite by using the GUI
- Make sure that you have installed the rewrite license.
- In the configuration utility, expand AppExpert, and right-click Rewrite, and then click Enable Rewrite feature.
Creating an HTTP Callout on the NetScaler Appliance
For more information about creating an HTTP callout, see Configuring an HTTP Callout. For more information about the parameter values, see Parameters and Values for HTTP-Callout-2 pdf.
Configuring the Rewrite Action
Create a rewrite action, Action-Rewrite-1, to replace the ESI content with the callout response body. Use the parameter settings shown in the following table.
Table 2. Parameters and Values for Action-Rewrite-1
Parameter | Value |
---|---|
Name | Action-Rewrite-1 |
Type | Replace |
Expression to choose target text reference | “HTTP.RES.BODY(500).AFTER_STR (\” |
String expression for replacement text | “SYS.HTTP_CALLOUT(HTTP-Callout-2)” |
To configure the rewrite action by using the configuration utility
- Navigate to AppExpert > Rewrite > Actions.
- In the details pane, click Add.
- In the Create Rewrite Action dialog box, in Name, type Action-Rewrite-1.
- In Type, select REPLACE.
-
In Expression to choose target text reference, type the following Advanced policy expression:
"HTTP.RES.BODY(500).AFTER_STR("<example>").BEFORE_STR("<example>")" <!--NeedCopy-->
-
In the String expression for replacement text, type the following string expression:
"SYS.HTTP_CALLOUT(HTTP-Callout-2)" <!--NeedCopy-->
- Click Create, and then click Close.
Creating the Rewrite Policy and Binding it Globally
Create a rewrite policy, Policy-Rewrite-1, with the parameter settings shown in the following table. You can create a rewrite policy in the Policies subnode and then bind it globally by using the Rewrite Policy Manager. Alternatively, you can use the Rewrite Policy Manager to perform both these tasks simultaneously. This demonstration uses the Rewrite Policy Manager to perform both tasks.
Table 3. Parameters and Values for Policy-Rewrite-1
Parameter | Value |
---|---|
Name | Policy-Rewrite-1 |
Action | Action_Rewrite-1 |
Undefined Result Action | -Global undefined-result action- |
Expression | “HTTP.REQ.HEADER(“Name”).CONTAINS (“Callout”).NOT” |
To configure a rewrite policy and bind it globally by using the configuration utility
- Navigate to AppExpert > Rewrite.
- In the details pane, under Policy Manager, click Rewrite Policy Manager.
- In the Rewrite Policy Manager dialog box, click Override Global.
- Click Insert Policy, and then, in the Policy Name column, click New Policy.
- In the Create Rewrite Policy dialog box, do the following:
1.In Name, type Policy-Rewrite-1.
- In Action, select Action-Rewrite-1.
- In Undefined-Result Action, select Global undefined-result action.
- In Expression, type the following Advanced policy expression:
"HTTP.REQ.HEADER("Name").CONTAINS("Callout").NOT" <!--NeedCopy-->
- Click Create, and then click Close.
- Click Apply Changes, and then click Close.
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.