# Disabling Caching

Many client and server applications cache resources to optimize sequential connections. Caching works through specific HTTP headers that instruct the client or the server to use a local copy of the response. This way, applications can load their content significantly faster than having to download the actual resources each time they are requested.

Whether you are a tester, quality engineer, or developer, you might often need to clear the cache using the built-in tools (for example, through the **Empty Cache and Hard Reload** feature in Chromium-based browsers) to ensure that you are seeing the latest version of the requested resources.

With Fiddler Everywhere, you can create a rule that automatically disables data caching. This allows you to test always against the latest version of your client/server API.

## Creating a "No Caching" Rule

Create a "No Caching" rule by setting the following actions through the [Rules Builder](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/modify-traffic-with-rules).

* Create an **Update Request Header** action and remove all pre-set values for the `If-Modified-Since` header.
* Create an **Update Request Header** action, and remove all pre-set values for the `If-None-Match` header.
* Create an **Update Request Header** action and set the `Pragma` header to `no-cache`.
* Create an **Update Request Header** action and set the `Cache-control` header to `no-cache`.
* Create an **Update Response Header** action and set the `Expires` header to `0`.
* Create an **Update Response Header** action and remove all pre-set values for the `Last-Modified` header.
* Create an **Update Response Header** action and remove all pre-set values for the `eTag` header.
* Create a **Update Response Header** action, and update the `Cache-Control` header with value `no-cache`.

This sample Fiddler rule matches all sessions and explicitly turns off the caching through.

![Creating "No Caching" rule](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/assets/b1f4bc863f1d1b20976414aa5451ee77/adv-tech-no-caching.png)

> tip The matching criteria in the above screenshot demonstrate how to apply the rule for all sessions. However, Fiddler Everywhere provides versatile matching conditions that you can use to further refine your web debugging process.

Once the rule is created, enable the **Rules** tab, toggle the rule switch, and start capturing traffic.

![Activating the "No Caching" rule](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/assets/55abb53341903b70f825d8aee0a16594/adv-tech-no-caching-active-rule.png)

Download a ready-to-use <a href="https://github.com/telerik/fiddler-everywhere/tree/master/rules/no-caching" target="_blank">"No Caching"</a> rule as a FARX file, which you can import through the Rules toolbar.

## See Also

* [Learn more about the Rules functionality in Fiddler Everywhere here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/modify-traffic-with-rules)
* [Learn more about all rules presets in Fiddler Everywhere here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/rules-presets)
* [Learn more on how to organize your rules here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/organizing-rules)
* [Learn more about the matching conditions here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/conditions-and-actions#conditions)
* [Learn more about the supported actions here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/conditions-and-actions#actions)
* [Learn more about final and non-final rules here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/conditions-and-actions#final-and-non-final-actions)
* [Learn more about using breakpoints here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/breakpoints)