MuleSoft · Web Service Consumer Connector
No Content-Type boundled in the message
Short answer
This error is thrown by Web Service Consumer Connector 1.10.0 and earlier when the response has no Content-Type. From version 1.10.1 it is not thrown when Content-Type is missing and the status is not 200, so upgrade the connector.
VerifiedLast verified
01Error text
No Content-Type boundled in the message02Likely causes
- The connector version is 1.10.0 or earlier and the service response has no
Content-Typeheader.
03How to fix it
- Check the connector version in the project's
pom.xml. - Upgrade Web Service Consumer Connector to 1.10.1 or later.
- Run the request again and handle the real error the service returns.
iNotes
The spelling "boundled" is how the message appears.
04Official documentation
→Related errors
- WSC:SOAP_FAULTWSC:SOAP_FAULT means the SOAP service returned a fault, or the response did not match the format in the WSDL. Read the fault text in error.errorMessage.payload.reason and the detail in error.errorMessage.payload.detail.
- WSC:EMPTY_RESPONSEWSC:EMPTY_RESPONSE occurs when mandatory fields are missing from the SOAP response (Illegal Empty Response). Inspect the HTTP status and headers on the error and check what the service actually returned.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer