Forum Discussion
set_device_name ?
i've already asked ES whether it's possible to have it in v10.x but haven't yet got answer.
Graham,
Expired Timestamp violation will indeed happen in this case. TS cookie set in response contains the encrypted timestamp which is compared by ASM with the current time on the next request. If TS cookie is "too old" (more than 600 seconds/10 minutes) Expired Timestamp violation will be generated - this prevents replay attacks (hackers using stolen HTTP requests of a user and then trying to replay them).
The expiration period can be controlled by cookie_expiration_time_out parameter in the ASM Advanced config.
Information about ASM cookies can be found here:
https://support.f5.com/csp/article/K6850
The config you are describing is problematic from ASM point of view, there should really be an irule redirecting requests to abcdef.com to xyz.abcdef.com
Hope this helps,
Sam