---
schema_version: "1"
id: f7bf4129c1ff92d2fef4d347931c3175f24046e0bd598b10eaca7aa041f58e42
title: HTTP Caching
collection: mulesoft
version: current
locale: ja-jp
portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/policies/http-caching-release-notes.md
canonical_url: https://docs.mulesoft.com/jp/release-notes/policies/http-caching-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 4ced35cd016785e2374ed874d11e1f7460893de551bbfef0db1f7ea0906c2308
description: MuleSoft Documentation Site
latest: true
---
# HTTP Caching

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

**October 1, 2026**

### What’s New

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

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

**October 3, 2025**

### What’s New

- Added metadata for using policies in Agent Fabric.

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

**July 29, 2022**

### What’s New

- The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters.

## [](#0-9-0)0.9.0

**May 17, 2022**

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

- Flex support for the Policy.

## [](#1-0-5)1.0.5

**November 10, 2021**

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

**Mule 4.1.0**

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

- Fixed an issue where an authentication object was incorrectly cached.

## [](#1-0-4)1.0.4

**November 20, 2020**

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

**Mule 4.1.0**

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

- When upgrading CloudHub Runtime version, policies that have the persistent cache enabled failed to deserialize elements.

## [](#1-0-3)1.0.3

**Apr 30, 2020**

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

**Mule 4.1.0**

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

- A `ClassCastException` error occurred when another policy added a response header to the payload. This issue is now resolved.

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

**September 12, 2019**

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

**4.1.0**

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

- An Object Store repeatedly fails to store an event, resulting in a stack overflow.

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

**April 26, 2019**

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

**4.1.0**

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

- Previous version incompatible with Mule Runtime 4.2.0 and greater.
- An error occurred when internal parameters were serialized. This is because these parameters are not serializable.
- During a cache hit, the loaded event was using the old context, such as event Id and correlation Id), resulting in failed error handling and feedback loop.

### [](#known-issues)Known Issues

- Upgrading from a previous policy version invalidates the existing cache.

## [](#1-0-0-deprecated)1.0.0 - Deprecated

**July 03, 2018**

### [](#compatibility)Compatibility

- v1.0.0 is compatible with v4.1.x and not compatible with v4.2.0 and greater of Mule Runtime.

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

**4.1.0**

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

- [Http Caching Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-http-caching)
- [Known Issues](https://help.salesforce.com/s/issues)