Threatening Content Filter Does Not Scan Content-* Headers

(Doc ID 1926665.1)

Last updated on AUGUST 18, 2016

Applies to:

Oracle API Gateway - Version 11.1.2 and later
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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms