How can we log a dependency between a blob and an asset, such that when the asset is updated the cached blob is invalidated? (Doc ID 1483696.1)

Last updated on NOVEMBER 20, 2023

Applies to:

Oracle WebCenter Sites - Version 7.6.2 and later
Information in this document applies to any platform.

Symptoms

When assets containing blobs are published, there are two observed behaviours:
1. blob IDs changes, so the new blobserver url for the blob is different from previous blobserver url, making it impossible to statically distribute blobserver urls.
2. The version of the blob on the old blobserver URL is still accessible.

Cause

	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

Symptoms

Cause

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

How can we log a dependency between a blob and an asset, such that when the asset is updated the cached blob is invalidated? (Doc ID 1483696.1)

Applies to:

Symptoms

Cause

To view full details, sign in with your My Oracle Support account.

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