It incurs problem when specifying vdisk-cache-related configs

[ddkkpp]

When I request the same content from ATS, the first request misses the cache and the response's date is current time, but the second request hits the cached content whose date is always 10 Apr 2019 15:55:04 GMT whenever it is hitted. Besides, requesting from the origin directly can obtain the content with current time.

[ddkkpp]

Another issue is that when a client requests content according to the wiki trace, the "Disk Used" and "Disk Total" statistics shown in the traffic_top command start out OK, but suddenly disappear midway, and the cache hit number is very small.

[ddkkpp]

If I comment out the vdisk cache related configuration (proxy.config.cache.vdisk_cache.algorithm) in the records.config, the above two problems will not occur and ATS works as expected.

[sunnyszy]

Hi @ddkkpp ,

For the 1st question, I think I hardcoded the timestamp in my implementation to bypass a bug.

For the 2nd one, I don't remember the details much... Sorry it has been to long that I couldn't help much on this.