Proxy Cache Changelog
Released changes to the Proxy Cache plugin (`proxy-cache`), newest release first.
21 released changes name proxy-cache, newest release first — 10 in Apache APISIX, 11 in API7 Gateway. Each row links to the change itself.
| Release | Date | Type | Change |
|---|
| 3.10.6 (opens in API7 Gateway docs) | 2026-08-25 | Fix | Fixed issue: In memory strategy, the storage key of a Vary variant was the cache key with the variant signature appended, and the cache key is derived from the request URI. A request crafted to carry another request's… (opens in API7 Gateway docs) |
| 3.10.6 (opens in API7 Gateway docs) | 2026-08-25 | Feature | Routes can now match the PURGE method, which is how Proxy Cache and GraphQL Proxy Cache invalidate a cached entry. The gateway has always accepted it; only the Dashboard's own schema rejected it, so a route serving ca… (opens in API7 Gateway docs) |
| 3.10.4 (opens in API7 Gateway docs) | 2026-07-27 | Feature | Added max_req_body_size and max_resp_body_size to bound how much of a request or response body a plugin reads into memory, defaulting to 67108864 bytes (64 MiB). A request body larger than the limit is rejected, and a… (opens in API7 Gateway docs) |
| 3.10.1 (opens in API7 Gateway docs) | 2026-06-15 | Fix | Graphql Proxy Cache: Fixed issue: After Vary support was added to the in-memory cache, a PURGE request cleared only the legacy cache slot and left the per-Vary variants cached, so stale responses were still served unt… (opens in API7 Gateway docs) |
| 3.10.0 (opens in API7 Gateway docs) | 2026-06-01 | Feature | The in-memory cache strategy now honors the Vary response header. Responses are cached per variant computed from the headers listed in Vary, and responses with Vary: * are not cached. (opens in API7 Gateway docs) |
| 3.9.19 (opens in API7 Gateway docs) | 2026-08-26 | Fix | Fixed issue: In memory strategy, the storage key of a Vary variant was the cache key with the variant signature appended, and the cache key is derived from the request URI. A request crafted to carry another request's… (opens in API7 Gateway docs) |
| 3.9.19 (opens in API7 Gateway docs) | 2026-08-26 | Feature | Routes can now match the PURGE method, which is how Proxy Cache and GraphQL Proxy Cache invalidate a cached entry. The gateway has always accepted it; only the Dashboard's own schema rejected it, so a route serving ca… (opens in API7 Gateway docs) |
| 3.9.17 (opens in API7 Gateway docs) | 2026-07-28 | Feature | Added max_req_body_size and max_resp_body_size to bound how much of a request or response body a plugin reads into memory, defaulting to 67108864 bytes (64 MiB). A request body larger than the limit is rejected, and a… (opens in API7 Gateway docs) |
| 3.9.14 (opens in API7 Gateway docs) | 2026-06-15 | Feature | The in-memory cache strategy now honors the Vary response header. Responses are cached per variant computed from the headers listed in Vary, and responses with Vary: * are not cached. (opens in API7 Gateway docs) |
| 3.9.13 (opens in API7 Gateway docs) | 2026-05-22 | Feature | Proxy Cache and GraphQL Proxy Cache: Added consumer_isolation and cache_set_cookie options to control the new safer cache behavior described in the upgrade note. (opens in API7 Gateway docs) |
| 3.8.8 (opens in API7 Gateway docs) | 2025-07-28 | Fix | Fixed issue: Inconsistent response headers for different strategies in the proxy-cache plugin. (opens in API7 Gateway docs) |
