Contact Us 1-800-596-4880
  1. Homepage
  2. Release Notes

  3. REST Proxies

REST Proxies

3.2.2

October 24, 2024

Minimum Mule Version

Mule 4.1.1

What’s New

  • Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.10.1.

    For more information about the HTTP Connector release, see HTTP Connector Release Notes - Mule 4.

3.2.1

August 5, 2024

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.9.3.

    For more information about the HTTP Connector release, see HTTP Connector Release Notes - Mule 4.

  • APIkit for Mule 4 has been upgraded to version 1.10.4.

    For more information about the APIkit release, see APIkit Release Notes.

2.2.1

August 5, 2024

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.9.3.

    For more information about the HTTP Connector release, see HTTP Connector Release Notes - Mule 4.

  • APIkit for Mule 4 has been upgraded to version 1.10.4.

    For more information about the APIkit release, see APIkit Release Notes.

3.2.0

February 7, 2024

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • This proxy version is now compatible with Java 17.

  • Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.9.0.

    For more information about the HTTP Connector release, see HTTP Connector Release Notes - Mule 4.

  • APIkit for Mule 4 has been upgraded to version 1.10.2.

    For more information about the APIkit release, see APIkit Release Notes.

2.2.0

February 7, 2024

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • This proxy version is now compatible with Java 17.

  • HTTP Connector upgraded to version 1.9.0.

  • APIkit for Mule 4 has been upgraded to version 1.10.2.

    For more information about the APIkit release, see APIkit Release Notes.

3.1.6

June 9, 2023

Minimum Mule Version

Mule 4.2.0

New Features and Enhancements

  • APIkit upgraded from version 1.7.0 to version 1.9.0.

3.1.5

November 17, 2022

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • HTTP Connector upgraded from version 1.6.0 to version 1.7.2.

3.1.4

October 11, 2022

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • APIkit upgraded from version 1.5.3 to version 1.7.0.

Fixed Issues

  • Parsing of unindented JSON files for OAS API Proxies failed in deployment.

3.1.3

Aug 10, 2022

Minimum Mule Version

Mule 4.1.1

Fixed Issues

Issue

ID

The published 3.1.2 artifact displayed the wrong version format in API Manager. Version 3.1.3 displays the correct version format.

W-11580215

3.1.2

June 1, 2022

Minimum Mule Version

Mule 4.1.1

Fixed Issues

  • Performing a POST request when the implementation times out no longer causes the original payload to be returned in the response.

3.1.1

December 7, 2021

New Features and Enhancements

  • HTTP Connector upgraded from version 1.5.25 to version 1.6.0.

3.1.0

February 02, 2021

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • APIkit upgraded from version 1.3.17 to version 1.4.2.

  • Added support for OAS 3.0.

Fixed Issues

  • The APIkit attributes validator was causing Heap memory leak issues.

3.0.2

November 02, 2020

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • APIKit upgraded from version 1.3.11 to version 1.3.17.

Fixed Issues

  • The REST Proxy was incorrectly parsing an OpenAPI JSON definition containing an URL query parameter with datatype int64 as string and not int.

  • The Content-Length header in the incoming request was not reaching the backend.

3.0.1

August 12, 2020

Minimum Mule Version

Mule 4.1.1

Fixed Issues

  • When no cipher suite is selected for the TLS configuration in Secret Manager, the proxy is generated with enabledCipherSuites="". This issue caused all requests to fail. (SE-15303)

3.0.0

Apr 30, 2020

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • HTTP Connector upgraded from version 1.5.7 to version 1.5.17.

  • Several performance improvements introduced.

  • Added annotation to ignore base path when applying Resource-Level policies.

Fixed Issues

  • When an HTTP request with an encoded path was processed, a path not found error occurred. The encoded path was first decoded and then encoded again, thereby modifying the original path in some cases.

2.1.2

December 14, 2021

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • APIKit upgraded from version 1.3.11 to version 1.3.17.

Fixed Issues

  • The REST Proxy was incorrectly parsing an OpenAPI JSON definition containing an URL query parameter with datatype int64 as string and not int.

  • The Content-Length header in the incoming request was not reaching the backend.

2.1.1

Apr 30, 2020

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • HTTP Connector upgraded from version 1.5.7 to version 1.5.17.

  • Several performance improvements introduced.

Fixed Issues

  • When an HTTP request with an encoded path was processed, a path not found error occurred. The encoded path was first decoded and then encoded again, thereby modifying the original path in some cases.

2.1.0

September 3, 2019

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • HTTP Connector upgraded from version 1.4.0 to version 1.5.7.

  • Performing validations for current request is now configurable.

Fixed Issues

  • Cookies for proxies are now disabled by default. To re-enable proxies:

    1. Import the proxy application to Anypoint Studio, and then modify the HTTP Request configuration.

    2. From HTTP Request Configuration > Settings, select the Enable cookies check box.

  • RestValidator does not correctly handle the 404 error.

2.0.0

January 8, 2019

This version uses REST Validator v2.0.0 with APIKit v1.2.0.

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • Introduced OAS support.

  • Introduced AMF parser support.

  • Parsers can now be configured by specifying the implementation.api.parser property. Permitted values inlcude: “AUTO”, “AMF”, or “RAML”. The default value is "AUTO".

  • When setting the keepApiBaseUri property to true, you can now retrieve the baseUri provided in the specification using the console. Otherwise, the console displays the baseUri of your local or CloudHub instance. The default value is "false".

  • Implemented the following checks:

    • disableValidations flag to enable or disable the parameters and payload validations. The default value is "false".

    • queryParamsStrictValidation flag to limit the allowed query parameters to those defined in the specifications. The default value is "false".

    • headersStrictValidation flag to limit the allowed HTTP headers to those defined in the specification. The default value is "false".

1.2.0

  • September 3, 2019*

Minimum Mule Version

Mule 4.1.1

New Features and Enhancements

  • HTTP Connector upgraded from version 1.4.0 to version 1.5.7.

  • Performing validations for current request is now configurable.

Fixed Issues

  • Cookies for proxies are now disabled by default. To re-enable proxies:

    1. Import the proxy application to Anypoint Studio, and then modify the HTTP Request configuration.

    2. From HTTP Request Configuration > Settings, select the Enable cookies check box.

  • RestValidator does not correctly handle the 404 error.

1.1.3

Nov 1, 2018

This version is deprecated. Use a non-deprecated version, with OAS support. This version uses RAML Validator v1.1.1 with APIKit v1.1.1.

New Features and Enhancements

  • Implemented the following checks:

    • disableValidations flag to enable or disable the parameters and payload validations. The default value is "false".

    • queryParamsStrictValidation flag to limit the allowed query parameters to those defined in the specifications. The default value is "false".

    • headersStrictValidation flag to limit the allowed HTTP headers to those defined in the specification. The default value is "false".

Known Issues

  • Because of the way the proxy URL is parsed, if duplicated paths are specified, the not duplicated portion of URL is taken into account. This occurs only for the last specified URL.

Minimum Mule Version

Mule 4.1.0

New Features and Enhancements

  • Improved TLS configuration to simplify using custom specifications.

1.1.2

May 14, 2018

This version is deprecated. Use a non-deprecated version, with OAS support. This version uses RAML Validator v1.1.1 with APIKit v1.1.1.

Known Issues

  • Because of the way the proxy URL is parsed, if duplicated paths are specified, only the last, not duplicated portion of it is taken into account.

Minimum Mule Version

Mule 4.1.0

New Features and Enhancements

  • Mule Maven Plugin is upgraded from version 3.1.0 to version 3.1.2.

1.1.1

Apr 16, 2018

This version is deprecated. Use a non-deprecated version, with OAS support. This version uses RAML Validator v1.1.1 with APIKit 1.1.1.

Minimum Mule Version

Mule 4.1.0

New Features and Enhancements

  • HTTPs request updated to include Keystore when making requests.

  • When a multi-part request is performed, default values are now added.

Fixed Issues

  • when a multi-part request was performed, a StreamClosedException error is generated .

  • when a resource is parameterized, a "Resource not found" error is generated.

Known Issues

  • Because of the way the proxy URL is parsed, if duplicated paths are specified, only the last, not duplicated portion of it is taken into account.

1.1.0

Jan 25, 2018

This version is deprecated. Use a non-deprecated version, with OAS support. This version uses RAML Validator v1.1.0 with APIKit v1.1.0.

Minimum Mule Version

Mule 4.1.0

New Features and Enhancements

  • Proxy refactored to enable editing using MuleSoft Anypoint Studio.

  • Properties are now parameterized and property names are now normalized.

Fixed Issues

  • Fixed error messages after adding error handler.

Known Issues

  • Because of the way the proxy URL is parsed, if duplicated paths are specified, the not duplicated portion of URL is taken into account. This occurs only for the last specified URL.

See Also

HTTP Connector release notes