How should the rewrite action add rewrite action sync_date replace http.res.date sys.time be interpreted?

• A. The rewrite action replaces the Date header in the http response with the GMT time stamp.
• B. The rewrite action replaces the Date header in the http response with the NetScaler system time in a conventional date format.
• C. The rewrite action is invalid because system time cannot be referenced in the system policy.
• D. The rewrite action replaces the NetScaler system time with the Date header in a conventional date format.

Answer: (B)

Interpreting this rewrite action, the Date header in the HTTP response is being replaced with the NetScaler system time. The http.res.date target refers to the response’s Date header, and sys.time supplies the appliance’s current clock value. When applied, the Date header is updated to reflect the system time and is presented in the conventional HTTP date format (RFC 1123), such as Wed, 21 Oct 2015 07:28:00 GMT. This is why the correct interpretation is that the response Date header is set to the NetScaler system time in a standard date format. The other options either describe the direction of the change incorrectly or imply a different representation (e.g., a plain GMT timestamp) that isn’t the standard HTTP date format.