Caching is usually a friend, but during debugging it can mask the real behaviour of an application. removeCacheAction clears the way so every exchange you capture reflects what the upstream service is actually returning right now, not what was returned the last time the client asked.
removeCacheAction is the right pick when caching is hiding the bug. By stripping cache directives from both directions, every request hits the upstream and every response is treated as new by the client.
Useful when:
Scope it tightly. Removing cache directives across an entire capture session can dramatically increase upstream load and slow down page loads.
Force every asset request through to the CDN origin so you can see exactly what is returned, with no 304 Not Modified short cuts.
rules:
- filter:
typeKind: HostFilter
pattern: cdn.example.com
actions:
- typeKind: RemoveCacheAction
Keep the rest of the site cached while you investigate a single endpoint that seems to return stale data.
rules:
- filter:
typeKind: FilterCollection
operation: And
children:
- typeKind: HostFilter
pattern: app.example.com
- typeKind: PathFilter
pattern: ^/static/main\.js
actions:
- typeKind: RemoveCacheAction
Ensure every API call during a release window goes to the origin without conditional revalidation, so you can compare fresh payloads between deploys.
rules:
- filter:
typeKind: HostFilter
pattern: api.internal.example.com
actions:
- typeKind: RemoveCacheAction
Remove all cache directive from request and response headers. This will force the clientto ask the latest version of the requested resource.
Evaluation scope defines the timing where this filter will be applied.
requestHeaderReceivedFromClient This scope occurs the moment fluxzy parsed the request header receiveid from client
removeCacheAction
This action has no specific characteristic
The following examples apply this action to any exchanges
Remove all cache directive from request and response headers. This will force the clientto ask the latest version of the requested resource.
rules:
- filter:
typeKind: AnyFilter
actions:
- typeKind: RemoveCacheAction
View definition of RemoveCacheAction for .NET integration.
This action has no related action
Cache related headers such as Cache-Control, Pragma, Expires, ETag, If-None-Match, and If-Modified-Since on both the request and the response. After the action runs, the exchange behaves as if no cache existed.
Indirectly. With no cache directives in the response, modern browsers will not store the resource for reuse, so the next request comes back through Fluxzy.
Yes. Strip the existing directives first and then add an explicit no-store header if you want to enforce a stricter policy on the client side.
It increases upstream load because every request bypasses the cache. Scope the filter to the host or path you are investigating to limit the impact.