A customer wants to comply with the best practice requirements of google lighthouse. Therefore the response headers for any Tealium resources should contain a fairly hight max-age value.
> When possible, cache immutable static assets for a long time, such as a year or longer.
Is there a way to adjust this server setting? There should be no negitive effects as the urls contain a parameter for the version to load anyways. (cache bust on template update)
Hi @MountainMaster as you mentioned we include a cache bust parameter by default (based on the current published version number) to ensure any change to a version always forces the client to request the latest version of the file.
Otherwise, some users could be running a different version of the configuration. This also means the utag files will be loaded with the same version from cache if no new versions have been published.
Summary: utag files have an explicit no-cache policy, which also means they are not immutable.
Hi @rebman ,
Thank you for you reply.
My request was not about the real caching behavior, wich is fine. Its about getting 100% in Google's Lighthouse rating. Therefore resources have to have a long Cache-Control HTTP response header.
So is there any chance to change these, as the no-cache policy is enforced over parameters anyways?