# Connector Code Bundle Changelog This document lists the versions of connector code bundles that work with the Native Node (MuleSoft, Cloudflare, etc.). ## Version format Connector code bundle versions follow this format: ```bash .. ``` | Element | Description | | ------- | ----------- | | `` | Significant updates, new features, or breaking changes. Requires a [Native Node update](https://docs.wallarm.com/updating-migrating/native-node/node-artifact-versions.md). | | `` | Enhancements or new features without breaking changes. | | `` | Minor bug fixes or enhancements. | ## MuleSoft Mule Gateway [How to upgrade](https://docs.wallarm.com/installation/connectors/mulesoft.md#upgrading-the-policy) The current version can be found in the `pom.xml` file of the downloaded Wallarm policy or in the policy information in the MuleSoft UI. | Policy version | [Native Node version](https://docs.wallarm.com/updating-migrating/native-node/node-artifact-versions.md) | | ------------------- | ------------------- | | 2.x | 0.8.2 and lower | | 3.0.x | 0.8.3 and higher | | 3.2.x | 0.10.1 and higher | ### 3.2.1 (2026-01-15) * Improved default host detection logic to be more robust when request headers are missing The default client host extraction expression now falls back from `X-Forwarded-Host` to the `Host` header and Mule server hostname (`server.host`). ### 3.2.0 (2025-01-31) Requires Native Node version 0.10.1 or higher. * The response code to blocked malicious requests is now set to 403 using the `http-transform` plugin from the MuleSoft Enterprise Edition repository Previously, a 200 status code was returned with a message indicating the request was blocked in the response body. Authentication for the `mulesoft-releases-ee` repository in your [Maven `settings.xml`](https://docs.wallarm.com/installation/connectors/mulesoft.md#2-obtain-and-upload-the-wallarm-policy-to-mulesoft-exchange) is now required in addition to the standard `anypoint-exchange-v3` repository to use the new connector version. * Bugfix: ensure the uniqueness of the request identifiers * Optimized memory consumption ### 3.0.1 (2024-11-20) * Added the `WALLARM NODE MAX RETRIES` and `WALLARM NODE RETRY INTERVAL` parameters These parameters allow users to configure the maximum number of retry attempts and the interval between retries when sending data to Wallarm Nodes during network failures. ### 3.0.0 (2024-11-14) Requires Native Node version 0.8.3 or higher. * Added the `CLIENT HOST EXPRESSION` and `CLIENT IP EXPRESSION` parameters They allow to specify custom [DataWeave](https://docs.mulesoft.com/dataweave/latest/dw-functions) expressions for extracting the original host and remote IP, aligning with [MuleSoft's IP Blocklist policy](https://docs.mulesoft.com/mule-gateway/policies-included-ip-blocklist). ### 2.0.3 (2024-11-13) * Bug fixes ### 2.0.2 (2024-11-06) * Bug fixes ### 2.0.1 (2024-10-10) * Initial release ## MuleSoft Flex Gateway [How to upgrade](https://docs.wallarm.com/installation/connectors/mulesoft-flex.md#upgrading-the-policy) The current version can be found in `Cargo.toml` → `[package]` → `version` parameter of the downloaded Wallarm policy or in the policy information in the MuleSoft UI. | Policy version | [Native Node version](https://docs.wallarm.com/updating-migrating/native-node/node-artifact-versions.md) | | ------------------- | ------------------- | | 1.x.x | 0.16.0 and higher | ### 1.4.0 (2026-04-09) * Upgraded Flex PDK to 1.7.0 ### 1.3.0 (2025-11-25) * Added the `verbose_logging` parameter to [Wallarm policy settings for Flex Gateway](https://docs.wallarm.com/installation/connectors/mulesoft-flex.md#configuration-options) — it enables extended debug logging to the standard Flex Gateway logging output Default: `false` (extended logging is disabled). * Fixed an issue where responses were sometimes not delivered to the Wallarm Node, resulting in a 400 error ### 1.2.0 (2025-10-20) * Added the `real_host_header` parameter to [Wallarm policy settings for Flex Gateway](https://docs.wallarm.com/installation/connectors/mulesoft-flex.md#configuration-options) — it defines which HTTP header is used to determine the original request host when traffic passes through a proxy or load balancer Default: `Host`. ### 1.1.1 (2025-09-29) * Extended MuleSoft logging with additional debug-level details ### 1.1.0 (2025-08-19) * Upgraded Flex PDK to 1.4.0 * Fixed Gateway crash on large responses ### 1.0.0 (2025-07-23) * [Initial release](https://docs.wallarm.com/installation/connectors/mulesoft-flex.md) ## Apigee [How to upgrade](https://docs.wallarm.com/installation/connectors/apigee.md#upgrading-the-policies) | Policy version | [Native Node version](https://docs.wallarm.com/updating-migrating/native-node/node-artifact-versions.md) | | ------------------- | ------------------- | | 1.x | 0.18.0 and higher | ### 1.0.1 (2205-11-05) * Enhanced the code bundle structure and flow naming ### 1.0.0 (2025-09-17) * [Initial release](https://docs.wallarm.com/installation/connectors/apigee.md) ## Akamai [How to upgrade](https://docs.wallarm.com/installation/connectors/akamai-edgeworkers.md#upgrading-the-wallarm-edgeworkers) The current version can be found in `wallarm-main`/`wallarm-sp` → `bundle.json` → `edgeworker-version` of the downloaded code bundle. | Policy version | [Native Node version](https://docs.wallarm.com/updating-migrating/native-node/node-artifact-versions.md) | | ------------------- | ------------------- | | 1.x | 0.16.3 and higher | ### 1.0 (2025-08-18) * [Initial release](https://docs.wallarm.com/installation/connectors/akamai-edgeworkers.md) ## CloudFront [How to upgrade](https://docs.wallarm.com/installation/connectors/aws-lambda.md#upgrading-the-lambdaedge-functions) ### 1.0.0 (2024-10-10) * Initial release ## Amazon API Gateway ### 1.0.0 (2025-12-17) * [Initial release](https://docs.wallarm.com/installation/connectors/aws-api-gateway.md) ## Cloudflare [How to upgrade](https://docs.wallarm.com/installation/connectors/cloudflare.md#upgrading-the-cloudflare-worker) ### 1.0.1 * Support custom blocking pages for malicious requests, configurable with the [parameters](https://docs.wallarm.com/installation/connectors/cloudflare.md#configuration-options): * `wallarm_block_page.custom_path` * `wallarm_block_page.html_page` * `wallarm_block_page.support_email` ### 1.0.0 (2024-10-10) * Initial release ## Kong Ingress Controller [How to upgrade](https://docs.wallarm.com/installation/connectors/kong-ingress-controller.md#upgrading-the-wallarm-lua-plugin) | Policy version | [Native Node version](https://docs.wallarm.com/updating-migrating/native-node/node-artifact-versions.md) | | ------------------- | ------------------- | | 1.0.x | 0.8.2 and higher | | 1.1.x | 0.22.0 and higher | ### 1.1.0 (2024-12-23) * Added support for the `inspect_response` and `inspect_response_body` [parameters](https://docs.wallarm.com/installation/connectors/kong-ingress-controller.md#configuration-options) to enable response and response body inspection ### 1.0.0 (2024-09-13) * Initial release ## Gloo Gateway ### 1.0.0 (2026-02-03) * [Initial release](https://docs.wallarm.com/installation/connectors/gloo.md) ## Broadcom Layer7 API Gateway [How to upgrade](https://docs.wallarm.com/installation/connectors/layer7-api-gateway.md#upgrading-the-wallarm-policies) ### 1.0.0 (2024-11-07) * Initial release ## Fastly [How to upgrade](https://docs.wallarm.com/installation/connectors/fastly.md#upgrading-the-wallarm-compute-service-on-fastly) ### 1.2.0 (2025-04-03) * Added ability to use alternative configurations If you run multiple Compute services for Wallarm, you can [create multiple config stores](https://docs.wallarm.com/installation/connectors/fastly.md#4-create-the-wallarm-config-store) with different configurations and link each of them to corresponding service. ### 1.1.0 (2025-01-06) * Added support for [log streaming endpoints](https://www.fastly.com/documentation/guides/integrations/logging/) with configuring via the optional `LOGGING_ENDPOINT` [parameter](https://docs.wallarm.com/installation/connectors/fastly.md#4-create-the-wallarm-config-store) ### 1.0.0 (2025-01-02) * Initial release ## IBM API Connect [How to upgrade](https://docs.wallarm.com/installation/connectors/ibm-api-connect.md#upgrading-the-policies) The current version can be found in the Wallarm policy file → `info.version`. Both policies use the same version number. | Policy version | [Native Node version](https://docs.wallarm.com/updating-migrating/native-node/node-artifact-versions.md) | | ------------------- | ------------------- | | 1.0.1 | 0.13.3 or later in the 0.13.x series, or 0.14.1 or later | ### 1.0.1 (2025-05-20) * Initial release ## Azure API Management [How to upgrade](https://docs.wallarm.com/installation/connectors/azure-api-management.md#upgrading-the-policies) The current version can be found in the Wallarm policy file → `X-Wallarm-Connector-Version` value. All policies use the same version number. | Policy version | [Native Node version](https://docs.wallarm.com/updating-migrating/native-node/node-artifact-versions.md) | | ------------------- | ------------------- | | 1.0.x | 0.18.0 and higher | ### 1.0.1 (2025-11-06) * Enhanced the code bundle structure and file naming ### 1.0.0 (2025-09-17) * [Initial release](https://docs.wallarm.com/installation/connectors/azure-api-management.md)