Changing CacheBust To Avoid Cache When Changing Customizations In Convergence (Doc ID 1558828.1)

Last updated on MARCH 04, 2016

Applies to:

Oracle Communications Convergence - Version 2.0 and later
Information in this document applies to any platform.

Goal

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.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms