FileSystemHttpCacheConfig (proto)

This extension has the qualified name envoy.extensions.http.cache.file_system_http_cache


This extension is work-in-progress. Functionality is incomplete and it is not intended for production use.

This extension has an unknown security posture and should only be used in deployments where both the downstream and upstream are trusted.


This extension extends and can be used with the following extension category:

This extension must be configured with one of the following type URLs:


This API feature is currently work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.


[extensions.http.cache.file_system_http_cache.v3.FileSystemHttpCacheConfig proto]

Configuration for a cache implementation that caches in the local file system.

By default this cache uses a least-recently-used eviction strategy.

  "manager_config": {...},
  "cache_path": ...

(extensions.common.async_files.v3.AsyncFileManagerConfig, REQUIRED) Configuration of a manager for how the file system is used asynchronously.


(string, REQUIRED) Path at which the cache files will be stored.

This also doubles as the unique identifier for a cache, so a cache can be shared between different routes, or separate paths can be used to specify separate caches.

If the same cache_path is used in more than one CacheConfig, the rest of the FileSystemHttpCacheConfig must also match, and will refer to the same cache instance.