The HTTP cache temporarily stores web documents (e.g. HTML pages, CCS documents, images) to reduce the latency induced by the server when it needs to serve up a page and/or reduce its workload.
When a client attempts to access a page, the corresponding web server will generate a page and send it over the network. Then the cache intercepts the response to store it in its local memory before serving it up to the customer.
When a request for the same page is sent by the same or another client, the cache will deliver it as it now has a copy of the requested resource. The web server will no longer be queried.
The standard’s specifications are set out in RFC 7234. The HTTP PURGE function is also proposed to delete an entry from the cache by calling it via its URL.
Icons: The Noun Project