1Y0-231 · Question #141
How can a Citrix Administrator configure a rewrite policy to change the version of HTTP from 1.1 to 1.0 in every request?
The correct answer is A. > add rewrite action RW_ACT replace http.req.version "\"HTTP/1.0\"". Option A is correct because it targets http.req.version - the request HTTP version - and replaces it with "HTTP/1.0", which is exactly the goal: downgrading outbound requests from 1.1 to 1.0. Option B uses the right expression (http.req.version) but replaces it with "HTTP/1.1"…
Question
How can a Citrix Administrator configure a rewrite policy to change the version of HTTP from 1.1 to 1.0 in every request?
Options
- A
add rewrite action RW_ACT replace http.req.version ""HTTP/1.0""
- 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.1""
- D
add rewrite action RW_ACT replace http.res.version ""HTTP/1.0""
How the community answered
(51 responses)- A84% (43)
- B8% (4)
- C2% (1)
- D6% (3)
Explanation
Option A is correct because it targets http.req.version - the request HTTP version - and replaces it with "HTTP/1.0", which is exactly the goal: downgrading outbound requests from 1.1 to 1.0.
Option B uses the right expression (http.req.version) but replaces it with "HTTP/1.1", leaving the version unchanged - it's a no-op against an already-1.1 request. Options C and D both use http.res.version, which targets the response (server-to-client traffic), not the request - so neither would affect what clients send to the server; additionally, Option C replaces with 1.1 rather than 1.0, making it doubly wrong.
Memory tip: Think REQ = Request (what the client sends), RES = Response (what the server returns). Since you want to modify what's going to the server, always use req. To remember the correct version value, anchor it to the goal: you're going down from 1.1 to 1.0, so the replacement must end in 0.
Topics
Community Discussion
No community discussion yet for this question.