To have a responder policy append '/mytraining' to every URL path, which combination of expression and type should be used?

• A. "(HTTP.REQ.URL.STARTSWITH(\"mytraining\"))" - REQUEST
• B. "(HTTP.REQ.URL.STARTSWITH(\"mytraining\"))" - RESPONSE
• C. "!(HTTP.REQ.URL.ENDSWITH(\"mytraining\"))" - REQUEST
• D. "!(HTTP.REQ.URL.ENDSWITH(\"mytraining\"))" - RESPONSE

Answer: (D)

The idea is to use a responder policy that runs on the response path and only acts when the URL path hasn’t already been modified. By evaluating the outgoing response, you can ensure the client sees a URL that ends with /mytraining, and you avoid adding the suffix again if it’s already present.

Using a negated ends-with check on the URL path means “if the path does not end with /mytraining, then apply the rewrite to append it.” This prevents duplicate suffixes. Applying this in the RESPONSE phase is appropriate because you’re shaping what the client ultimately receives, not what is sent to the backend. If you used a starts-with test, you’d be focusing on the beginning of the path rather than the ending, which isn’t what you want when ensuring a particular suffix is present. And choosing REQUEST would modify the path before the server sees it, which is not aligned with controlling the client-facing URL in this scenario.

So, the best match is a responder policy evaluated on the RESPONSE path with the expression that negates ENDSWITH("mytraining"), ensuring the suffix is appended only when it’s not already present.