To protect the HTTP backend header without removing the header, which rewrite action type should be applied?

To protect the HTTP backend header without removing the header, which rewrite action type should be applied?

• A. REPLACE
• B. CORRUPT_HTTP_HEADER
• C. REPLACE_HTTP_REQ
• D. REPLACE_ALL

Answer: (A)

When you want to keep the header in place but make its content safe, you modify the header value rather than removing it. Using a REPLACE action in a rewrite policy lets you substitute the existing header value with a new, safe string (for example, a sanitized or encoded version) while the header line stays in the HTTP request to the backend. This preserves compatibility with the backend and prevents header-based issues without deleting the header. The other options don’t fit: corrupting the header would break it on purpose; replacing the HTTP request would affect more than just the header content; and replacing all would apply changes broadly rather than to the specific header you want to protect.

When you want to keep the header in place but make its content safe, you modify the header value rather than removing it. Using a REPLACE action in a rewrite policy lets you substitute the existing header value with a new, safe string (for example, a sanitized or encoded version) while the header line stays in the HTTP request to the backend. This preserves compatibility with the backend and prevents header-based issues without deleting the header. The other options don’t fit: corrupting the header would break it on purpose; replacing the HTTP request would affect more than just the header content; and replacing all would apply changes broadly rather than to the specific header you want to protect.