Why /content/published/api/v1.1/assets/[...id...]/native... API Returning 400 Instead of Expected 404?
(Doc ID 3024946.1)
Last updated on MAY 27, 2024
Applies to:
Oracle Content Management - Version N/A and laterContent and Experience Cloud Service - Version N/A and later
Content and Experience Cloud Classic - Version 18.4.1 and later
Information in this document applies to any platform.
Goal
Typically when this api is using an invalid id, a 404 is returned:
In this scenario when invalid id is %uff0e%uff0e%u2215, why does it return 400 instead of 404?
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 |