Which Citrix ADC policy is best suited for manipulating content in HTTP requests and responses, such as URL paths or headers?

Which Citrix ADC policy is best suited for manipulating content in HTTP requests and responses, such as URL paths or headers?

• A. Responder
• B. Rewrite
• C. Redirect
• D. Monitor

Answer: (B)

Manipulating HTTP request and response content is what the Rewrite policy is built for. It lets you modify parts of the messages as they pass through Citrix ADC, including the URL path, query strings, headers, and even the body. This enables tasks like normalizing URLs, adding or removing headers, or changing specific header values so backend servers see the exact content you intend. If you only needed to tell the client to fetch from another URL, a Redirect would be used instead, and if you wanted to generate a custom response or block traffic, a Responder would be appropriate. Monitor, meanwhile, is for checking the health of back-end services. So for direct content changes in requests and responses, Rewrite is the right fit.

Manipulating HTTP request and response content is what the Rewrite policy is built for. It lets you modify parts of the messages as they pass through Citrix ADC, including the URL path, query strings, headers, and even the body. This enables tasks like normalizing URLs, adding or removing headers, or changing specific header values so backend servers see the exact content you intend. If you only needed to tell the client to fetch from another URL, a Redirect would be used instead, and if you wanted to generate a custom response or block traffic, a Responder would be appropriate. Monitor, meanwhile, is for checking the health of back-end services. So for direct content changes in requests and responses, Rewrite is the right fit.