Hi Serena,
All our assets are "soft-cached" in general. Web Messenger assets follow the cache control settings which is `cache-control: max-age=0, no-cache`.
But this doesn't mean that we re-fetch the complete asset every time, but rather do a soft-check to see if anything is changed from the previous one:
Even without the cache-control headers, our hosting does provide Etag headers, which means the full data is not requested every time by the browser. There is a request, but the browser will send an If-None-Match header, and the server will respond with `Etag` header which is cross-checked. If they are same, meaning nothing has changed, so there is no any transfer of data. It's not optimal, but it's not as slow as a full re-fetch.

This is required for us to check if something has changed from the last deploy, so any new deploy changes are automatically reflected for you. This applies to all Web Messenger CDN assets. Hope this clarifies.
Thanks,
Ranjith Sai
------------------------------
Ranjith Manikante Sai
Senior Manager, Development
------------------------------
Original Message:
Sent: 04-10-2025 10:01
From: Serena Spaccesi
Subject: Cache-control in genesys.min.js - Web Messenger Integration
Hi @Angelo Cicchitto,
thanks for the question. This change are to optimise the performance.
Can you help me?
Thank you
------------------------------
Serena Spaccesi
Indra Italia spa
------------------------------
Original Message:
Sent: 04-08-2025 00:15
From: Angelo Cicchitto
Subject: Cache-control in genesys.min.js - Web Messenger Integration
Hi Serena - what are you trying to solve with this suggested change?
------------------------------
Angelo Cicchitto
Genesys - Employees