---
schema_version: "1"
id: a812fa3292fd8368cc0446f633913267e848da4a047d31b99d09ed9feb81329b
title: Spike Control
collection: mulesoft
version: current
locale: ja-jp
portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/policies/spike-control-release-notes.md
canonical_url: https://docs.mulesoft.com/jp/release-notes/policies/spike-control-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 0baf102bd4a5411ca2c909fd93e74dfee8535caad6411da7498ebf7e7e2cfd9a
description: MuleSoft Documentation Site
latest: true
---
# Spike Control

## [](#1-2-3)1.2.3

**October 1, 2026**

### What’s New

- This release updates policy metadata only. There’s no functional change.

## [](#1-1-6)1.1.6

**October 27, 2023**

### [](#fixed-issues)Fixed issues

- Policy can now be applied alongside Rate Limiting.

## [](#1-2-1)1.2.1

**May 26, 2022**

### [](#fixed-issues-2)Fixed issues

- Fix policy schema not allowing additional properties via REST API.

## [](#1-2-0)1.2.0

**May 17, 2022**

### [](#new-features-and-enhancements)New Features and Enhancements

- First Flex compatible Policy.
- Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration.

## [](#1-1-5)1.1.5

**Apr 30, 2020**

### [](#minimum-mule-version)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements-2)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.

### [](#fixed-issues-3)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).

<table><tbody><tr><td class="icon"><i class="fa icon-note" title="Note"></i></td><td class="content">Because a critical issue was found in the last validation stage, the Spike Control policy v1.1.4 has been deprecated and removed from production.</td></tr></tbody></table>

## [](#1-1-3)1.1.3

**August, 2019**

### [](#minimum-mule-version-2)Minimum Mule Version

**4.1.0**

### [](#new-features-and-enhancements-3)New Features and Enhancements

- Several performance improvements are introduced in this release.

### [](#fixed-issues-4)Fixed Issues

- When using a SOAP proxy, an incorrect return code is passed.

## [](#1-1-2)1.1.2

**April 26, 2019**

### [](#minimum-mule-version-3)Minimum Mule Version

**4.1.0**

### [](#new-features-and-enhancements-4)New Features and Enhancements

- Several performance improvements are introduced in this release.

## [](#1-1-1)1.1.1

**March 16, 2018**

### [](#minimum-mule-version-4)Minimum Mule Version

**4.1.0**

### [](#new-features-and-enhancements-5)New Features and Enhancements

- Added the `violationCategory` parameter in the YAML configuration file for Feedback Loop.

### [](#fixed-issues-5)Fixed Issues

- The Rate Limiting policy is rejected from the scheduler during high network traffic.

## [](#1-1-0)1.1.0

**January 25, 2018**

### [](#minimum-mule-version-5)Minimum Mule Version

**4.1.0**

## [](#see-also)See Also

- [Spike Control](https://docs.mulesoft.com/gateway/latest/policies-included-spike-control)
- [Known Issues](https://help.salesforce.com/s/issues)