Threatening Content Filter Does Not Scan Content-* Headers
(Doc ID 1926665.1)
Last updated on JULY 21, 2023
Applies to:
Oracle API Gateway - Version 11.1.2.3.0 to 11.1.2.3.0 [Release 11gR1]
Information in this document applies to any platform.
Symptoms
In Oracle API Gateway (OAG) 11.1.2.3.0 and earlier, the Threatening Content filter does not scan Content-* headers.
Changes
The Threatening Content filter scans headers only if the checkbox labeled "Additional message parts to scan: HTTP Headers" is checked.
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! |
In this Document
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.