Currently, URLs generated in XML/JSON/HTML contents are static. This implies that if the website caches the files, it is not possible to empty this cache, we have to wait for the expiration. That's why I suggest implementing a cacheBustingQueryParam option: a query paramater added to all URLs that acts as a cache busting system.
The contents that would be affected by this option are the following:
favicons(iconFilePath, {
// We don't write the question mark at the beginning: it would be better to add it automatically.
cacheBustingQueryParam: 'v=1',
// Options...
});
I hope this option will suit you, because I think it can be very useful in many cases. Other libraries already use this kind of options, e.g. TinyMCE (see https://www.tiny.cloud/docs/configure/integration-and-setup/#cache_suffix). If ever the Favicons maintainers accept this enhancement, I will offer to develop it myself in a pull request!
Hi,
Introduction
Currently, URLs generated in XML/JSON/HTML contents are static. This implies that if the website caches the files, it is not possible to empty this cache, we have to wait for the expiration. That's why I suggest implementing a
cacheBustingQueryParam
option: a query paramater added to all URLs that acts as a cache busting system.The contents that would be affected by this option are the following:
browserconfig.xml
(fromresponse.files
)manifest.webmanifest
(fromresponse.files
)yandex-browser-manifest.json
(fromresponse.files
)*.html
(fromresponse.html
)Current behavior
Input (
favicon.js
):Output (
metadata.html
):Requested behavior
Input (
favicon.js
):Output (
metadata.html
):Conclusion
I hope this option will suit you, because I think it can be very useful in many cases. Other libraries already use this kind of options, e.g. TinyMCE (see https://www.tiny.cloud/docs/configure/integration-and-setup/#cache_suffix). If ever the Favicons maintainers accept this enhancement, I will offer to develop it myself in a pull request!