MTOM Not Using Correct content-type With SOAP 1.2 Message in Oracle API Gateway (Doc ID 2148696.1)

Last updated on JUNE 16, 2016

Applies to:

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

Symptoms

When processing a SOAP 1.2 message that has an MTOM attachment in OAG, the content-type is supposed to be application/soap+xml after processing, but the gateway is using a content-type of text/xml (which is the value for SOAP 1.1) after applying the API Gateway MTOM filter.

The specifications are as follows:

Soap 1.1 with MTOM:
SOAP 1.1 Binding for MTOM 

The type parameter of the content-type header of the root part MUST specify a content-type of text/xml.
Soap 1.1 uses the namespace http://schemas.xmlsoap.org/soap/envelope/

Soap 1.2 with MTOM:
Serialization of a SOAP message

The type parameter of the content-type header of the root part MUST specify a content-type of "application/soap+xml".
SOAP 1.2 uses the namespace http://www.w3.org/2003/05/soap-envelope


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