My Oracle Support Banner

XSLT Transformation Filter Removes The Content ID In Multipart Messages (Doc ID 1592139.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.

Symptoms

Oracle API Gateway (OAG) 11.1.2.1.0 or 11.1.2.2.0.

In a multipart message, there is an optional sub-component of the content-type header called "start" which points to the first main body part of the multipart message.
This "start" parameter contain a Content-ID, which is also in the multipart parts of the main body, like this:

Content-Type: multipart/related; boundary="MIMEBoundary_c46b02ecf074e1b835adf738b0e6469b25a0b72789bc6407"; type="application/soap+xml"; start=""; action="ebms3"
[...]
--MIMEBoundary_c46b02ecf074e1b835adf738b0e6469b25a0b72789bc6407
Content-Type: application/soap+xml; charset=UTF-8
Content-Transfer-Encoding: binary
Content-ID:


When the problem occurs, the Content-ID header inside of the MIMEBoundary is missing.

This then causes a variety of further error messages from libxml.

The problem shows up only when an XSLT Transformation Filter is used.

Changes

The problem does not occur with OAG 11.1.2.3.0.

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.