Swarm cache mechanism

Nodes that do not store a replica of a requested object on disk may also read the object from another node and cache it locally. For popular "hot" objects that are read very frequently, this will result in copies being cached on more and more nodes of the cluster, until eventually every node holds a cached copy, resulting in higher throughput for such hot objects.

If you would like to make sure an object is not being read from cache, you can use the following in your request:

-H "Cache-Control: no-cache"