A Citrix Administrator complains that between the two rewrite policies bound to the vserver, only one policy, whichever has lower priority, works. The other policy is never used.
Click the 'Exhibit' button to view the screenshot of the relevant policy binding.
What is the cause of the issue?
The issue is caused by the 'Goto Expression' value for Policy RP_remove_srv_header being configured as 'END'. When the 'Goto Expression' is set to 'END', the evaluation of any further policies stops. In this scenario, because RP_remove_srv_header has a higher priority (lower numeric value), it gets evaluated first and stops any subsequent policy evaluations, leading to the issue where only the policy with the lower numeric value is ever used.
B - You can specify the priority of the policy to indicate the Go to Expression policy; you cannot use the name of the policy. If you want the NetScaler to stop evaluating other policies after evaluating a particular policy, you can set the Go to Expression to ‘END’. https://docs.citrix.com/en-us/netscaler/12/appexpert/rewrite/how-rewrite-works.html
I confirm, B is the correct one because of the END expression. But i'm not sure if the "Lower priority" in the question mean the rule with 100.. Because the number is lower but the priority is higher.. so question need to be clearer.
My bad -> whichever has lower priority -> So the answer stay B because the two policies have the END expression.
Lowest policy has END stated so engine stops with policy processing