Loading
Salesforce now sends email only from verified domains. Read More

How to Enable HTTP Wire Logging for HTTP Connector or Other Connectors Using HTTP Service for Mule Applications

Publish Date: Mar 5, 2026
Task

In Mule applications, enable DEBUG logging for inbound/outbound HTTP traffic handled by connectors utilizing the HTTP Service:

  • HTTP Connector
  • Web Services Consumer Connector / CXF Module
  • Salesforce Connector
  • Many others...

Important:

  • Enable DEBUG logging only for troubleshooting. Avoid leaving it enabled indefinitely or unsupervised, as it can negatively impact API performance.
  • The debug logs will display HTTP headers and payload in plain text.
Steps

Refer to How to Set the Log Level for a Mule Application in Different Environments to enable DEBUG logging for the following package:

For Mule 4.x APIs:

  • org.mule.service.http.impl.service.HttpMessageLogger

Mule Runtime 4.1.4 and later versions allow you to debug only specific HTTP Listener or Request configurations:

  • HTTP Listener: Assuming your HTTP Listener configuration is named “CUSTOM_NAME”, set DEBUG logging level for the following package:
    • org.mule.service.http.impl.service.HttpMessageLogger.CUSTOM_NAME
  • HTTP Request: Assuming your HTTP Request configuration is named “CUSTOM_NAME2”, set DEBUG logging level for the following package:
    • org.mule.service.http.impl.service.HttpMessageLogger.http.requester.CUSTOM_NAME2

The custom names used in these examples are the “name” attributes of the “http:listener-config” or “http:request-config” XML items.

For Mule 3.x APIs, set DEBUG logging level for the following packages:

  • org.mule.module.http.internal.HttpMessageLogger
  • com.ning.http

Further Debug Logging for Mule

If you need to troubleshoot more details about the HTTP service (not just the payload/headers), please refer to How to enable all HTTP Service debug modes? - Enhanced HTTP Wire Logging for Mule 4 APIs.

Knowledge Article Number

001115102

 
Loading
Salesforce Help | Article