---
schema_version: "1"
id: bc5a7b241c5b35d6c0e06418c9e723aa11086a1d6e95419633d29fd2cc120340
title: Legacy IP Blocklist
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/policies/legacy-ip-blocklist-policy-release-notes.md
canonical_url: https://docs.mulesoft.com/release-notes/policies/legacy-ip-blocklist-policy-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: d6b007c303303d400d7a57c32dab3b5e379b09f9c82f21b9bdfe354037280465
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
keywords: mule, ip-blacklist, policy, release notes
---

# Legacy IP Blocklist

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

**Jul 30, 2021**

Legacy IP Blocklist policy has been deprecated after fixing inclusive terminology issues. It will
still continue to execute properly in production. Fixes and new features will be released in the
[IP Blocklist policy](https://docs.mulesoft.com/gateway/latest/policies-included-ip-blocklist).

## 1.2.2

**Apr 30, 2020**

### Minimum Mule Version

**Mule 4.1.0**

### New Features and Enhancements

- Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2.

- Performance improvements are introduced to the header manipulation engine.

- Several performance improvements are introduced in the policy error handling.

### Fixed issues

- After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of
  case-sensitivity:

  [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2).

- Removed `commons-beanutils` dependency from the policy jar file to maintain security compliance.

## 1.2.1

**Jul 23, 2019**

### Minimum Mule Version

**Mule 4.1.0**

### New Features and Enhancements

- Several performance improvements are introduced in this release.

### Known Issues

- An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to
  applications that have the mule-secure-configuration-property-module plugin configured. To resolve
  this issue, upgrade the specified plugin in the application to version 1.1.0.

### Fixed Issues

- The remoteAddress for HTTP Connectors were not being parsed for versions greater than 1.4.0. This
  issue is now resolved.

## 1.2.0

**Apr 26, 2019**

### Minimum Mule Version

**Mule 4.1.0**

### New Features and Enhancements

- Introduced support to encrypt sensitive information related to the policy. The Runtime version
  must be properly configured and must support encryption. Encryption is supported starting with
  Mule Runtime v4.2.0.

- Several performance improvements are introduced in this release.

### Known Issues

- An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to
  applications that have the mule-secure-configuration-property-module plugin configured. To resolve
  this issue, upgrade the specified plugin in the application to version 1.1.0.

## 1.1.1

**Jun 05, 2018**

### Minimum Mule Version

**Mule 4.1.0**

### New Features and Enhancements

Added `violationCategory` in the YAML configuration for Feedback Loop.

## 1.1.0

**Jan 25, 2018**

### Minimum Mule Version

**4.1.0**

### New Features and Enhancements

- Reduced error-handling verbosity in templates.

- Added default expression for IP Addresses in the YAML file instead of in the template.

### Fixed Issues

When a WSDL proxy received an empty payload, or an invalid XML, an ExpressionRuntimeException error
was generated. This issue is now resolved.

## 1.0.0

**Nov 14, 2017**

### Minimum Mule Version

**4.0.0**

## See Also

- [IP Blocklist Policy](https://docs.mulesoft.com/gateway/latest/policies-included-ip-blocklist)

- [Known Issues](https://help.salesforce.com/s/issues)