Which configuration correctly rewrites the HTTP request version to 1.0 in every request using a rewrite policy?

Which configuration correctly rewrites the HTTP request version to 1.0 in every request using a rewrite policy?

• A. add rewrite action RW_ACT replace http.res.version "HTTP/1.1"
• B. add rewrite action RW_ACT replace http.req.version "HTTP/1.1"
• C. add rewrite action RW_ACT replace http.res.version "HTTP/1.0"
• D. add rewrite action RW_ACT replace http.req.version "HTTP/1.0"

Answer: (D)

To rewrite the HTTP request version, you need to modify the request’s version field, not the response. The field that controls the version in the incoming request is http.req.version, and using a replace action to set it to "HTTP/1.0" changes the version reported in every client request as it passes through the policy. This affects only the request path, so every request will appear as HTTP/1.0 to the backend. The other options target the response version (http.res.version) or set the request version to HTTP/1.1, which does not meet the goal of forcing HTTP/1.0 in every request.

To rewrite the HTTP request version, you need to modify the request’s version field, not the response. The field that controls the version in the incoming request is http.req.version, and using a replace action to set it to "HTTP/1.0" changes the version reported in every client request as it passes through the policy. This affects only the request path, so every request will appear as HTTP/1.0 to the backend.

The other options target the response version (http.res.version) or set the request version to HTTP/1.1, which does not meet the goal of forcing HTTP/1.0 in every request.