Scenario:
POLICY 1:
add rewrite action ACT_1 corrupt_http_header Accept-Encoding
add rewrite policy POL_1 HTTP.REQ.IS_VALID ACT_1
POLICY 2:
add rewrite action ACT_2 insert_http_header Accept-Encoding `\`identity\`` add rewrite policy POL_2 `HTTP.REQ.IS_VALID ` ACT_2
How can a Citrix Administrator successfully bind the above rewrite policies to the load-balancing vServer lb_vsrv so that POL_2 is evaluated after POL_1 is evaluated?
In Citrix ADC, policy priorities work in reverse order, meaning the higher the number, the lower the priority. Therefore, policies with lower numerical priorities are evaluated first. To ensure that POL_2 is evaluated after POL_1, POL_1 must be assigned a lower numerical priority and should therefore be evaluated first. By setting POL_1 with priority 90 and POLICY 2 with priority 100, we achieve this sequence. The 'gotoPriorityExpression NEXT' ensures that after POL_1 is evaluated, the next policy in line (POL_2) will be evaluated. 'gotoPriorityExpression END' for POL_2 implies no further policies need to be evaluated. This configuration ensures POL_2 is evaluated after POL_1.
I hope its B. In the Citrix ADC operating system, policy priorities work in reverse order—the higher the number, the lower the priority.
I prefer B B. bind lb vServer lb_vsrv -policyName POL_1 -priority 90 -gotoPriorityExpression NEXT -type REQUEST bind lb vServer lb_vsrv -policyName POL_2 -priority 100 -gotoPriorityExpression END -type REQUEST pol1 has lower priority with next, pol 2 has higher prio with end so pol1 would go first then pol2 as questions asks
B is correct : - Pol1 has a prio of 90 so it's evaluated first -gotoPrioExpression NEXT means that it will evaluate next item in the policy list - Pol2 has a prio of 100, so it"s avaluated after Pol1
In the Citrix ADC operating system, policy priorities work in reverse order - the higher the number, the lower the priority. For example, if you have three policies with priorities of 10, 100, and 1000, the policy assigned a priority of 10 is applied first, then the policy assigned a priority of 100, and finally the policy assigned an order of 1000.
B is correct : - Pol1 has a prio of 90 so it's evaluated first -gotoPrioExpression NEXT means that it will evaluate next item in the policy list - Pol2 has a prio of 100, so it"s avaluated after Pol1