--- schema_version: "1" id: 2bd7a92b6c548e9a092ca9790063a1cbe789c28862823f5a60c48c37ce11ec49 title: HTTP Connector Release Notes collection: mulesoft version: current locale: ja-jp portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/connector/connector-http.md canonical_url: https://docs.mulesoft.com/jp/release-notes/connector/connector-http source_site: docs.mulesoft.com content_type: documentation content_hash: e0b9e1eb933d69ea32b2f0ecb1cd5b7eb70f3caf9b553d4f7ace82c179cd29d8 description: MuleSoft Documentation Site latest: true --- # HTTP Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for HTTP (HTTP Connector) enables you to declare HTTP servers that listen to requests and trigger flows, as well as HTTP clients that can communicate with any HTTP service. Guide: [HTTP Connector User Guide](https://docs.mulesoft.com/http-connector/latest/) ## [](#1-12-1)1.12.1 **August 18, 2026** ### Fixed Issues
Issue Resolution ID

The plugins used for packaging the connector are updated to generate complete and accurate metadata at build time.

W-23815437
### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-12-0)1.12.0 **August 4, 2026** ### What’s New - The connector now reports a validation warning at deployment time when an `http:listener-config` is declared but isn’t referenced by any **Listener**, helping you detect orphaned listener configurations. ### Fixed Issues
Issue Resolution ID

The Response Timeout and the connection pool acquisition timeout no longer conflict.

W-23131874

HTTP request URL validation at deployment time no longer produces false warnings when the request path or URL is set using a property placeholder.

W-23049232

Carriage return and line feed (CR/LF) characters in HTTP header values are now sanitized instead of causing the message to be rejected.

W-22252135

Requests canceled because the graceful shutdown period expired now return an HTTP 503 (Service Unavailable) response instead of an HTTP 500 (Internal Server Error) response.

W-21580619

The HTTP Connector proxy configuration no longer logs unnecessary WARN messages on Mule 4.9 and earlier runtime versions.

W-21948326

The Grizzly library is upgraded to 2.3.36-MULE-031.

W-21337433

The Sockets Connector dependency is upgraded to 1.2.9.

W-21770069
### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-11-3)1.11.3 **May 14, 2026** ### What’s New - The release 1.11.3 addresses a regression introduced in release 1.11.2, and includes all fixes from that release. ### Fixed Issues
Issue Resolution ID

Build failures caused by an incorrectly published pom.xml in Exchange for HTTP Connector 1.11.2 are now fixed. The malformed POM caused the mule-maven-plugin to incorrectly resolve dependencies, resulting in the package org.mule.extension.socket.api.socket.tcp being exported by both the HTTP and Sockets connectors.

W-22489693
### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-11-2-deprecated)1.11.2 (Deprecated) **May 12, 2026** ### Fixed Issues
Issue Resolution ID

The plugins used for packaging are updated to fix a connector metadata generation issue related to Java 17 compatibility.

W-20903962
### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-11-1)1.11.1 **January 15, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Spring dependencies are now removed from HTTP Connector and are only present in internal test modules.

W-19774918

A potential NullPointerException error that occurred during Abstract Syntax Tree (AST) validations at deployment time is now resolved, ensuring more stable application deployments.

W-20064897

The HTTP Connector Listener operation now correctly enforces the protocol version setting. Previously, a configuration set to HTTP/1 only incorrectly allowed incoming HTTP/2 connections.

W-19889726

HTTP Connector no longer adds erroneous Transfer-Encoding headers to HTTP/2 responses.

W-19845365
## [](#1-11-0)1.11.0 **October 3, 2025** ### What’s New - The connector supports HTTP/2 (experimental in Mule runtime 4.10.0 and subject to change), enabling faster and more efficient HTTP communication. See [HTTP/2 Support](https://docs.mulesoft.com/http-connector/latest/http-2-support). ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-10-6)1.10.6 **September 30th, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now avoids unnecessary internal thread jumps when handling small payloads.

W-19545477

Request headers are now injected correctly for Visualizer.

W-19564419

Internal dependencies are upgraded.

W-19772921
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues)