From c02b6f45dd5fc33d31b6c940ec3e784b2a050f76 Mon Sep 17 00:00:00 2001 From: Aydin Hassan Date: Tue, 11 Feb 2025 14:40:17 +0100 Subject: [PATCH] Update cache clearing methods --- guides/hosting/infrastructure/reverse-http-cache.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/guides/hosting/infrastructure/reverse-http-cache.md b/guides/hosting/infrastructure/reverse-http-cache.md index a6a0db6d7..d3fc76b2f 100644 --- a/guides/hosting/infrastructure/reverse-http-cache.md +++ b/guides/hosting/infrastructure/reverse-http-cache.md @@ -195,8 +195,12 @@ For manual deployment, you can find the VCL Snippets here: The Reverse Proxy Cache shares the same invalidation mechanism as the Object Cache and has the same tags. So, when a product is invalidated, the object cache and the HTTP cache will also be invalidated. -::: warning -`bin/console cache:clear` will also clear the HTTP cache. If this is not intended, you should manually delete the `var/cache` folder. The object cache can be cleared with `bin/console cache:pool:clear --all` explicitly. -::: +There are a few different cache clearing commands: + +1. `bin/console cache:clear` - Clears and warms up the application cache +2. `bin/console cache:clear:all` - Clears everything, including application cache, cache pools and the HTTP cache +3. `bin/console cache:clear:http` - Clears the reverse proxy cache if enabled, if not it clears the `http` cache pool + +If you only want to clear the http cache, use `bin/console cache:clear:http` - \ No newline at end of file +