![Caching explained using wireshark http](https://cdn2.cdnme.se/5447227/9-3/5_64e61dfa9606ee7f6350b87c.png)
![caching explained using wireshark http caching explained using wireshark http](https://jeffreyeverhart.com/wp-content/uploads/2017/05/server-side-cache.jpg)
The caching directives are specified in a comma-separated list. These directives typically override the default caching algorithms. The Cache-Control header allows a client or server to transmit a variety of directives in either requests or responses. We use the Cache-Control header for this purpose. The basic cache mechanisms in HTTP/1.1 are implicit directives to caches where server-specifies expiration times and validators. The goal of caching in HTTP/1.1 is to eliminate the need to send requests in many cases, and to eliminate the need to send full responses in many other cases. The HTTP/1.1 protocol includes a number of elements intended to make caching work.
![caching explained using wireshark http caching explained using wireshark http](https://hanselmanblogcontent.azureedge.net/Windows-Live-Writer/6ea3738aa1ca_111D0/image_1eb5631f-accf-4e3f-acd1-138e2e91c992.png)
HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches.
![Caching explained using wireshark http](https://cdn2.cdnme.se/5447227/9-3/5_64e61dfa9606ee7f6350b87c.png)