这怎么可能？对于同一个文件，Date / Expires / Last-Modified标头是如此截然不同。即使该文件今天（4月8日）被修改，它也随机返回4月7日和4月3日或4日之后！
curl -I http://storage.googleapis.com/myappname.appspot.com/config/config.json
HTTP/1.1 200 OK
X-GUploader-UploadID: AEnB2UoPjuz3v6i-RioExWbgl1JULi-FqGuXlljVXfQBCa3Xg5aSAGm9SslQu1m2I9ITSE6223FgsNjTiBMr4aS-QBeDumyv89n87pAnPpII7wffRZtCW70
Date: Sat, 07 Apr 2018 18:18:55 GMT
Expires: Sun, 07 Apr 2019 18:18:55 GMT
Last-Modified: Sat, 07 Apr 2018 17:25:44 GMT
ETag: "0a8411662813a125f999edad6079d7a5"
x-goog-generation: 1523121944356178
x-goog-metageneration: 1
x-goog-stored-content-encoding: identity
x-goog-stored-content-length: 41487
Content-Type: application/json
x-goog-hash: crc32c=x7F/0g==
x-goog-hash: md5=CoQRZigToSX5me2tYHnXpQ==
x-goog-storage-class: STANDARD
Accept-Ranges: bytes
Content-Length: 41487
Server: UploadServer
Cache-Control: no-cache
Age: 57035
curl -I http://storage.googleapis.com/myappname.appspot.com/config/config.json
HTTP/1.1 200 OK
X-GUploader-UploadID: AEnB2UpWhRGTwxsME436eKKeSf507oBN4mfT9MZLknOVb92GdRmV-Cs8z8UTVDvoENIeN6fq9PL9A3HkRLgVIWJFhzfVM4Ysy4xz20ZS1Z-Ez18i1islc1o
Date: Wed, 04 Apr 2018 13:34:51 GMT
Expires: Thu, 04 Apr 2019 13:34:51 GMT
Last-Modified: Wed, 04 Apr 2018 07:14:23 GMT
ETag: "522c4e9f5f97873f930501b69da311cf"
x-goog-generation: 1522826063699049
x-goog-metageneration: 1
x-goog-stored-content-encoding: identity
x-goog-stored-content-length: 40298
Content-Type: application/json
x-goog-hash: crc32c=ZhnEqg==
x-goog-hash: md5=UixOn1+Xhz+TBQG2naMRzw==
x-goog-storage-class: STANDARD
Accept-Ranges: bytes
Content-Length: 40298
Server: UploadServer
Cache-Control: Cache-Control:no-cache
Age: 333838
它只是拒绝返回最近对该文件所做的更改，即使在很长时间之后也是如此。
更新： TRACEROUTE
traceroute to storage.googleapis.com (216.58.197.80), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.544 ms 1.582 ms 1.973 ms
2 10.247.0.1 (10.247.0.1) 5.637 ms 5.641 ms 5.624 ms
3 broadband.actcorp.in (202.83.20.173) 5.609 ms 6.521 ms 6.524 ms
4 broadband.actcorp.in (202.83.20.181) 6.520 ms 6.534 ms 6.941 ms
5 broadband.actcorp.in (202.83.20.50) 11.394 ms 11.889 ms 11.881 ms
6 72.14.194.18 (72.14.194.18) 45.704 ms 42.574 ms 42.644 ms
7 * 108.170.253.113 (108.170.253.113) 42.576 ms *
8 108.170.237.95 (108.170.237.95) 43.536 ms 108.170.236.197 (108.170.236.197) 45.852 ms 45.865 ms
9 maa03s21-in-f16.1e100.net (216.58.197.80) 45.847 ms 43.914 ms 45.781 ms
截至今天（4月10日），我仍然看到：
Date: Wed, 04 Apr 2018 15:35:28 GMT
Expires: Thu, 04 Apr 2019 15:35:28 GMT
Last-Modified: Wed, 04 Apr 2018 07:14:23 GMT
ETag: "522c4e9f5f97873f930501b69da311cf"
x-goog-generation: 1522826063699049
x-goog-metageneration: 1
x-goog-stored-content-encoding: identity
x-goog-stored-content-length: 40298
Content-Type: application/json
x-goog-hash: crc32c=ZhnEqg==
x-goog-hash: md5=UixOn1+Xhz+TBQG2naMRzw==
x-goog-storage-class: STANDARD
Accept-Ranges: bytes
Content-Length: 40298
Server: UploadServer
Cache-Control: Cache-Control:no-cache
Age: 528505
然而，从我的办公室网络，我看到了该文件的更新版本，但即便如此，它也不尊重“无缓存”指令并偶尔显示陈旧数据。
答案 0 :(得分：0)
免责声明，我致力于Google云平台支持，希望您发现这些信息非常有用。
目前，工程团队已经意识到这个问题，他们目前正在高度优先地对其进行调查。
请注意：
自2013年11月11日美国/太平洋地区2018-04-11以来，Google云端存储缓存标记有缓存控制：no-cache的对象问题已得到解决。标记为缓存控制的对象可能已被缓存，可能会受到影响，直到2018-04-19星期四，但可以使用解决方法。
提供的解决方法：