In a responder policy that rewrites the incoming URL, the policy type used when binding should be REQUEST or RESPONSE?

In a responder policy that rewrites the incoming URL, the policy type used when binding should be REQUEST or RESPONSE?

• A. REQUEST
• B. RESPONSE
• C. BOTH
• D. EITHER

Answer: (A)

Rewriting the URL that a client sends happens as the request is being processed, before any back-end server selection or routing decisions are finalized. In Citrix ADC, this means you must bind the responder policy to the request path, so it runs on the incoming request. A policy bound to the request path can modify the URL that will be sent to the backend, ensuring the rewrite takes effect for subsequent routing and processing. If you bound the policy to the response path, it would run after a response has been generated by the server, which would not affect the incoming URL at all and is appropriate for altering pieces of the response (like headers or content) instead of the request itself. Therefore, the correct approach is to bind the responder policy as a REQUEST.

Rewriting the URL that a client sends happens as the request is being processed, before any back-end server selection or routing decisions are finalized. In Citrix ADC, this means you must bind the responder policy to the request path, so it runs on the incoming request. A policy bound to the request path can modify the URL that will be sent to the backend, ensuring the rewrite takes effect for subsequent routing and processing. If you bound the policy to the response path, it would run after a response has been generated by the server, which would not affect the incoming URL at all and is appropriate for altering pieces of the response (like headers or content) instead of the request itself. Therefore, the correct approach is to bind the responder policy as a REQUEST.