In the rewrite policy example, the request version is rewritten to which value?

In the rewrite policy example, the request version is rewritten to which value?

• A. HTTP/1.0
• B. HTTP/1.1
• C. HTTP/2.0
• D. HTTP/3.0

Answer: (A)

The rewrite policy is showing how you can force the incoming HTTP request to use a specific version for downstream handling. In this example, the request is rewritten to HTTP/1.0. Rewriting to HTTP/1.0 guarantees the backend sees the simplest, legacy-style request without the extra features of newer HTTP versions—no HTTP/1.1 keep-alives, host header expectations, or chunked transfer encoding. This improves compatibility with backends or intermediaries that expect HTTP/1.0 semantics or can’t properly handle newer features. Using a newer version would enable capabilities the backend might not support, leading to potential compatibility issues.

The rewrite policy is showing how you can force the incoming HTTP request to use a specific version for downstream handling. In this example, the request is rewritten to HTTP/1.0. Rewriting to HTTP/1.0 guarantees the backend sees the simplest, legacy-style request without the extra features of newer HTTP versions—no HTTP/1.1 keep-alives, host header expectations, or chunked transfer encoding. This improves compatibility with backends or intermediaries that expect HTTP/1.0 semantics or can’t properly handle newer features. Using a newer version would enable capabilities the backend might not support, leading to potential compatibility issues.