In the rewrite policy example, which header is inserted into every REQUEST?

In the rewrite policy example, which header is inserted into every REQUEST?

• A. HTTP_HEADER_SSL_PARAMETER inserted in every RESPONSE
• B. HTTP Header "SSL_parameter: icauser@mylab.lab" will be inserted in every REQUEST
• C. HTTP Header "SSL_parameter: C=IN, ST=KA, O=Mylab, CN=icauser@mylab.lab" will be inserted in every RESPONSE
• D. HTTP Header "SSL_parameter: C=IN, ST=KA, O=Mylab, CN=icauser@mylab.lab" will be inserted in every REQUEST

Answer: (D)

Rewrite policies modify traffic by injecting headers into requests or responses. In this example, the header named SSL_parameter carries the client certificate subject and is inserted into every request. The value includes the certificate subject fields like C (country), ST (state), O (organization), and CN (common name), specifically "C=IN, ST=KA, O=Mylab, CN=icauser@mylab.lab". This lets backend services see the client's identity on every call for auth, auditing, or personalization. The header is placed in each request, not in responses. Other options would either target responses or use a different, incomplete header value, which is why this one is the correct approach.

Rewrite policies modify traffic by injecting headers into requests or responses. In this example, the header named SSL_parameter carries the client certificate subject and is inserted into every request. The value includes the certificate subject fields like C (country), ST (state), O (organization), and CN (common name), specifically "C=IN, ST=KA, O=Mylab, CN=icauser@mylab.lab". This lets backend services see the client's identity on every call for auth, auditing, or personalization.

The header is placed in each request, not in responses. Other options would either target responses or use a different, incomplete header value, which is why this one is the correct approach.