OCM CDN (Akamai) HTTP Status Code Change Request From 200 to 404 (Error) Page
(Doc ID 2899365.1)
Last updated on APRIL 10, 2024
Applies to:
Oracle Content Management - Version 22.6.1 and laterInformation in this document applies to any platform.
Goal
Use Case: Users or crawlers can for some reason try to access an URL of our OCM Sitebuilder Site that does not resolve in a proper page. In this case the configured Error Page of the site kicks in. This Error Page is delivering a 200 HTTP Status Code back to the browser. It should be a 404 HTTP Status code instead, i.e. it reads 404 on the content, but the HTTP status code is 200.
The proposed solution is to handle the switch from HTTP 200 to HTTP 404 at the CDN Akamai level. We are using the Oracle provided CDN Akamai to cache our site. And while Akamai seems to have this capability in general, it is unclear if Oracle has the possibility to do such an adjustment with Akamai.
Can you please help finding this out and ideally also implement this switch?
Solution
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
Goal |
Solution |
References |