Changing CacheBust To Avoid Cache When Changing Customizations In Convergence
(Doc ID 1558828.1)
Last updated on OCTOBER 15, 2019
Applies to:Oracle Communications Convergence - Version 2.0 and later
Information in this document applies to any platform.
On : Convergence 2-6.01
Is there a way to change the cacheBust number (cacheBustId) returned by Convergence to notify the client browser and proxy that the file has changed? This will help to avoid issues due to cached files when changing customizations.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document