Between two rewrite policies bound to a vServer, only one policy works; what is the cause of the issue?

Between two rewrite policies bound to a vServer, only one policy works; what is the cause of the issue?

• A. GotoExpression value for Policy RP_remove_srv_header is configured as 'END'.
• B. The Invoke label is NOT configured.
• C. The Policy expression of the no_chunk_pol is 'true' and 'NOT HTTP.REQ.IS_VALID'.
• D. The Priority of the no_chunk_pol is a higher numeric value than 100.

Answer: (A)

The issue comes from how rewrite policy flow is controlled. When two rewrite policies are bound to a vServer, each policy can run in sequence, but the GotoExpression on a policy determines whether the chain continues. If the GotoExpression for the first policy is configured as END, the system stops evaluating any further rewrite policies for that request. That means the second policy never executes, so only the first policy’s changes take effect. To have both policies apply, you’d use a flow that continues to the next policy (for example, NEXT) or adjust the bindings accordingly. Brief notes on the others: not configuring an Invoke label won’t inherently stop the second policy from running; the policy expression of the no_chunk_pol affects whether it runs under certain conditions but doesn’t automatically halt the chain; and a higher numeric priority for the second policy changes order but doesn’t by itself cause the chain to terminate.

The issue comes from how rewrite policy flow is controlled. When two rewrite policies are bound to a vServer, each policy can run in sequence, but the GotoExpression on a policy determines whether the chain continues. If the GotoExpression for the first policy is configured as END, the system stops evaluating any further rewrite policies for that request. That means the second policy never executes, so only the first policy’s changes take effect.

To have both policies apply, you’d use a flow that continues to the next policy (for example, NEXT) or adjust the bindings accordingly.

Brief notes on the others: not configuring an Invoke label won’t inherently stop the second policy from running; the policy expression of the no_chunk_pol affects whether it runs under certain conditions but doesn’t automatically halt the chain; and a higher numeric priority for the second policy changes order but doesn’t by itself cause the chain to terminate.