Which command sequence changes HTTP version to 1.0 for all requests?

Which command sequence changes HTTP version to 1.0 for all requests?

• A. >add rewrite action RW_ACT replace http.res.version ( \"HTTPS/1.1\" ) > add rewrite policy RW_POL true RW_ACT
• B. >add rewrite action RW_ACT replace http.req.version ( \"HTTPS/1.1\" ) > add rewrite policy RW_POL true RW_ACT
• C. >add rewrite action RW_ACT replace http.res.version ( \"HTTPS/1.0\" ) > add rewrite policy RW_POL true RW_ACT
• D. >add rewrite action RW_ACT replace http.req.version ( \"HTTPS/1.0\" ) > add rewrite policy RW_POL true RW_ACT

Answer: (D)

Modifying the version used by client requests requires changing the request side, not the response. You need a rewrite action that replaces the request version field (http.req.version) and set it to the desired value, here HTTPS/1.0. To apply to every request, pair that action with a rewrite policy that always evaluates to true (no condition). This makes the change apply universally to all requests. The correct sequence therefore uses http.req.version set to HTTPS/1.0 with an always-true policy. The other options either target the response version (http.res.version) or set the request version to HTTPS/1.1, which does not meet the requirement of changing all requests to 1.0.

Modifying the version used by client requests requires changing the request side, not the response. You need a rewrite action that replaces the request version field (http.req.version) and set it to the desired value, here HTTPS/1.0. To apply to every request, pair that action with a rewrite policy that always evaluates to true (no condition). This makes the change apply universally to all requests. The correct sequence therefore uses http.req.version set to HTTPS/1.0 with an always-true policy. The other options either target the response version (http.res.version) or set the request version to HTTPS/1.1, which does not meet the requirement of changing all requests to 1.0.