Content-Length Header Is Not Populated When Going Direct At Sites On OCM Bypassing The CDN
(Doc ID 2975086.1)
Last updated on SEPTEMBER 20, 2023
Applies to:
Oracle Content Management - Version N/A and laterInformation in this document applies to any platform.
Goal
Content-Length header is not populated when going direct at sites on OCM bypassing the CDN.
When you access a site via the CDN:
https://example.ocecdn.oraclecloud.com/site/<sitename>/
the content-length header is always filled in for all requests.
When you access the same site from OCM (non-CDN):
https://example.ocecdn.oraclecloud.com/site/<sitename>/
the content-length header is not populated.
Why the content-length header handled differently.
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 |