RSS Is Caching 404 Response For Vanity URLs That Do Not Exist (Doc ID 2018002.1)

Last updated on APRIL 30, 2021

Applies to:

Symptoms

When accessing a vanity url that does not exist yet, the vanity url returns a 404 response. This vanity url/404 response is cached in the RSS Vanity Url cache.  Even after creating the same vanity url from an existing asset, if accessing the vanity url in a browser via RSS again, still returns a 404 as the response was already cached. The RSS Vanity Url cache needs to be flushed first, before the vanity url would be able to return a valid response.

Below is an example:

1. There is a static page with hard link of an invalid vanity url, as the asset for it does not exist yet: '/test/yetToPublishVanityUrlPage'

2. Next access the non existing page using the vanity url through RSS.
  
e.g. http://deliveryrss:port/test/yetToPublishVanityUrlPage

3. RSS returns 404 response. And there should be entry in the RSS Vanity URL cache for this page such as:

deliveryrss:port/test/yetToPublishVanityUrlPageThursday, May 14, 2015 16:46:52 PM EDT    Thursday, May 14, 2015 16:46:52 PM EDT    asset-null:null

4. Now create a page asset & set the vanity URL to 'yetToPublishVanityUrlPage' on Source environment and then publish to Delivery environment
 
5. Now try again accessing above page using the same vanity URL (http://deliveryrss:port/test/yetToPublishVanityUrlPage)

6. Response is going to be still 404 and RSS Vanity Url cache needs to be flushed to see the page.

Changes

Cause

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