After Renaming A Site, It Is Not Rendering The Custom URL Or Direct URL
(Doc ID 2391093.1)
Last updated on MARCH 20, 2024
Applies to:
Content and Experience Cloud Service - Version N/A and later Information in this document applies to any platform.
Symptoms
A CEC site that had its site name recently changed is no longer accessible. Accessing the internal URL https://<service instance>-<identity domain>.sites.<dc>.oraclecloud.com/<site name> results in browser console output:
Status 404 returned from /_cache_<value>/structure.json with response:
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
The browser console will show:
controller.js:1:2198 SCS.logError https://<service instance>-<identity domain>.sites.<dc>.oraclecloud.com/<old site name>/_cache_bd22/_sitesclouddelivery/renderer/controller.js:1:2198 SCS.onRenderError https://<service instance>-<identity domain>.sites.<dc>.oraclecloud.com/<old site name>/_cache_bd22/_sitesclouddelivery/renderer/controller.js:1:2111 SCS.callService/this.xmlhttp.onreadystatechange https://<service instance>-<identity domain>.sites.<dc>.oraclecloud.com/<old site name>/_cache_bd22/_sitesclouddelivery/renderer/controller.js:1:11191
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!
