WSO2Con 2013 CFP Banner

Error : "Transport level information does not match with SOAP Message namespace URI"

By Eran Chinthaka
Date: Thu, 25th Jan, 2007
Level:
Reads: 24527 Discuss this article on Stack Overflow

Q: Why do I get the error, "Transport level information does not match with SOAP Message namespace URI" in Apache Axis2/Java?

chinthaka's picture
Eran Chinthaka
Software Engineer
WSO2 Inc.

A: When Apache Axis2/Java receives a SOAP message, Axis2 tries to determine the SOAP version this message adheres to. This is required for the validation purposes against the correct SOAP specification. Axis2 has two basic mechanisms to identify the SOAP version.

  1. Checking the namespace of the SOAP envelope. If the namespace is "http://schemas.xmlsoap.org/soap/envelope/", then it is a SOAP 1.1 message, and if the namespace is "http://www.w3.org/2003/05/soap-envelope", then it is a SOAP 1.2 message.
  2. If the transport medium is HTTP, Then we check for the existance of SOAPAction HTTP Header. If the message is SOAP 1.1, then there must be a SOAPAction HTTP header. If it is a SOAP 1.2 message, then there may be a SOAPAction parameter inside the Content-type header (this parameter is not mandatory according to SOAP 1.2 specification HTTP binding)

When both the above parameters are present, Axis2 compares the outputs from those evaluations. If they do not match, then Axis2 will throw an error saying "Transport level information does not match with SOAP Message namespace URI". So if you encounter this error, check your SOAP message and HTTP headers.

Applies To:

Apache Axis2/Java v1.0 and higher

WSO2Con 2014