Solved! Go to Solution.
@iwan_uswak I'm guessing you're asking this question because a google Page Speed Insights report has shown that utag.js has a short cache control header value? The reason for this is to ensure that when you publish in Tealium iQ, that your visitors always get the latest version of the utag.js files. This is a global setting, and cannot be changed on a per-account basis, as @thyngster correctly stated.
The result of this header is that the browser will check for a new file once the 5 minute period has expired, but if the file has not been modified, our multi-CDN network returns a "304 - Not Modified" response, which instructs the browser to load the file from cache, and results in only a very minimal amount of data transfer (just header data), since the utag files do not need to be retransmitted.
I hope this adequately explains the reasons for this header setting. It is therefore safe to ignore any warnings about it in page speed reports, since it is not really having a significant effect on your page load. Please let me know if anything is unclear.
Learn more about how Universal Tag (utag.js) files are cached in the browser.
is your explanation already valid or are there some news?
I received a request to increase cache period for utag.js file, utag.sync file and I wuold like to know if it is ok to answer that this is a global setting and cannot be changed on a per-account basis.
Thank you very much