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

MuleSoft error
No Content-Type boundled in the message

02Likely causes

  • The connector version is 1.10.0 or earlier and the service response has no Content-Type header.

03How to fix it

  1. Check the connector version in the project's pom.xml.
  2. Upgrade Web Service Consumer Connector to 1.10.1 or later.
  3. Run the request again and handle the real error the service returns.

iNotes

The spelling "boundled" is how the message appears.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.