大网数据广告活动
网站运营与故障问答

What happens if you don't set cache-control header?

· 52CE 我爱测

What happens if you don't set the cache-control header? Does HTTP specify a default behaviour that clients should follow or is it up to the clients to decide? In Chrome, I have seen some Javascript requests that have no cache-con…

问题原文

原帖链接 · Nishant · CC BY-SA 3.0

What happens if you don't set the cache-control header? Does HTTP specify a default behaviour that clients should follow or is it up to the clients to decide?

In Chrome, I have seen some Javascript requests that have no cache-control headers showing up as 200 (from disk cache). Is Chrome optimizing this?

In IE, I have seen it show up as a 304 (not modified).

How do I understand this better?

已采纳解答

原帖链接 · Tim Fountain · CC BY-SA 4.0

If there is no Cache-Control header and no Expires header, but there is a Last-Modified header (which most web servers send by default for static assets), most browsers will use heuristic freshness to determine how long to cache that asset for.

The typical calculation for this (which is the one suggested by RFC 7234) is:

(current time - last modified time) / 10

So, for example, if the last modified time for an image states it was last changed 60 days ago, a browser might decide it could reasonably use the locally cached version of that image for 6 days before checking for a new version.

Note that in most cases, if you hit refresh, you are telling the browser to fetch a fresh version, so in that situation this logic wouldn't apply.

Freshness as determined by actual browsers:

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2017-12-08)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0 / CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。