Which rewrite action type should be used to protect the HTTP header without removing it?

Which rewrite action type should be used to protect the HTTP header without removing it?

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

Answer: (A)

The key idea is to modify the content of an HTTP header without removing the header itself. The REPLACE rewrite action is designed for precisely this: it substitutes a matched string within the HTTP message (such as a header value) with a new value, while preserving the header line so the header remains present in the request or response. This lets you protect or mask sensitive header information without stripping the header away. Why this fits better than the others: CORRUPT_HTTP_HEADER would deliberately break or invalidate the header, which is not desirable when you want to keep the header intact while changing its content. REPLACE_HTTP_REQ would rewrite the whole HTTP request, potentially altering more than just a single header. REPLACE_ALL would apply replacements broadly across the message, risking unintended changes elsewhere. REPLACE targets only the targeted content, keeping the header in place and preserving the overall request/response structure.

The key idea is to modify the content of an HTTP header without removing the header itself. The REPLACE rewrite action is designed for precisely this: it substitutes a matched string within the HTTP message (such as a header value) with a new value, while preserving the header line so the header remains present in the request or response. This lets you protect or mask sensitive header information without stripping the header away.

Why this fits better than the others: CORRUPT_HTTP_HEADER would deliberately break or invalidate the header, which is not desirable when you want to keep the header intact while changing its content. REPLACE_HTTP_REQ would rewrite the whole HTTP request, potentially altering more than just a single header. REPLACE_ALL would apply replacements broadly across the message, risking unintended changes elsewhere. REPLACE targets only the targeted content, keeping the header in place and preserving the overall request/response structure.