A redirect loop occurs when a Responder policy redirects root page requests to the home page. Which policy expression should be used to fix it?

• A. http.REQ.URL.Contains("/")
• B. http.REQ.URL.EQ("/")
• C. Change Responder action expression to "/"
• D. Change Responder Action expression to http.REQ.URL.

Answer: (B)

When you want to fix a redirect loop caused by sending root page requests to the home page, you must trigger the redirect only for the exact root URL. Using an exact match ensures the policy fires only when the request path is exactly “/” and not for other pages.

The expression that does this is an exact equality check on the URL path, http.REQ.URL.EQ("/"). It returns true only when the requested path is exactly “/”, so other pages like “/home” or “/about” won’t be redirected, preventing the loop.

If you used a broader test like http.REQ.URL.Contains("/"), the condition would match nearly every URL (since all paths include a slash), causing many redirects and likely a loop between pages. Changing what the policy does (the redirection target) without fixing when the policy fires wouldn’t resolve the looping behavior; the trigger needs to be an exact root-path match.