Hi, @luksak. Again, there is a feature request filed for this but this is the same issue you have already reported. There is nothing new happening here.
I do see you requesting the file 1000 times in just over one minute (71 seconds). I’m showing all 1000 were cache hits.
There were only 12 cache misses for that URL in the 2 hour time window for the URL in the har file. The request in the HAR file was after two minutes of no traffic for that URL and the response size was 631140 bytes (including headers).
The following factors were likely involved from it being removed from the cache:
- there had been little traffic for the URL before the burst of 1000 requests
- 100% of the requests (all 1012) were from a single IP address
- it is a large asset (over 0.5 MB)
All of those factors contributed to the asset dropping out of the cache in the time window between the burst and the HAR file request.
This is also why we don’t expose a header to show what is or isn’t cached. We don’t want people to attempt manipulate the cache with inorganic traffic as you have done. It doesn’t work and we don’t want people wasting time on it for that reason.
If the feature request does become available, we will follow-up here to let you know.
If you want to remove Large Media from this site, please read the following support guide and let us know when you are ready to proceed: