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 cause of the issue is that the GotoExpression value for Policy RP_remove_srv_header is configured as ‘END’. When a policy with a lower priority runs and its GotoExpression is set to END, the policy processing stops. This means that any subsequent policies (with higher priority numeric values) are not evaluated, causing only the policy with the lower numeric priority to work correctly.
A. Lowest policy has END stated so engine stops with policy processing. Should be set to NEXT
A or C depending on how you interpret the question. A is the answer if the evaluation is based on the screenshot. C is the answer if you take into account that the question says that whichever policy has the lower priority,works. The right answer would be to have NEXT as GoToExpression for both policies, not only for RP_remove_svr_header