Html HTTP 304 Not Modified-responses 是否应该包含缓存控制标头？
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/1587667/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Should HTTP 304 Not Modified-responses contain cache-control headers?
提问by runarM
I've tried to understand this, and searched SO for similar questions, but I still don't have a 100% understanding on how this is supposed to work.
我试图理解这一点，并搜索了类似的问题，但我仍然没有 100% 了解它应该如何工作。
I get this response on a request for an image resource:
我在请求图像资源时收到此响应：
Response Headers
Server Apache-Coyote/1.1
Date Mon, 19 Oct 2009 09:04:04 GMT
Expires Mon, 19 Oct 2009 09:06:05 GMT
Cache-Control public, max-age=120
Etag image_a70703fb393a60b6da346c112715a0abd54a3236
Content-Disposition inline;filename="binary-216-420"
Content-Type image/jpg;charset=UTF-8
Content-Length 4719
The desired behavior is that the client should cache this for 120 seconds, then request it from the server again. Within the 120 seconds, no request is sent to the server.
期望的行为是客户端应该缓存它 120 秒，然后再次从服务器请求它。在 120 秒内，没有请求发送到服务器。
Then, after 120 seconds, a request is sent and a 304 response is received:
然后，120 秒后，发送请求并收到 304 响应：
Response Headers
Server Apache-Coyote/1.1
Date Mon, 19 Oct 2009 09:06:13 GMT
Request Headers
Host localhost:8080
User-Agent Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Accept image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language en-us,no;q=0.8,sq;q=0.7,en;q=0.5,sv;q=0.3,nn;q=0.2
Accept-Encoding gzip,deflate
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive 300
Connection keep-alive
Referer http://localhost:8080/cms/site/0/en/home
Cookie JSESSIONID=768ABBE1A3BFABE3B535900233330650; versionsCssDisplayState=block; iceInfo=iceOn:false,activePortletKey:,icePagePanelX:1722,icePagePanelY:3
If-None-Match image_a70703fb393a60b6da346c112715a0abd54a3236
So far, all well. But then, on the next request (whithin 120 seconds) i would have thought that the resource should be cached for 120 new seconds. What i see in the browser (Firefox) on the other hand, is that it from this point on always request the resource and receives the 304-response.
到目前为止，一切顺利。但是，在下一个请求（在 120 秒内）时，我会认为资源应该被缓存 120 秒。另一方面，我在浏览器（Firefox）中看到的是，从现在开始，它始终请求资源并接收 304 响应。
Am I supposed to attach the cache-control headers in the 304-response? From what i can read in the spec, it seems like the cache-control settings should be omitted, and that the cache should cache it for 120 new seconds automatically?
我应该在 304 响应中附加缓存控制标头吗？从我在规范中可以读取的内容来看，似乎应该省略缓存控制设置，并且缓存应该自动将其缓存 120 新秒？
采纳答案by Justin Ludwig
In theory you shouldn't have to send Cache-Control for a 304 -- the recipient should just continue to use the cache directives that it received from the original 200. However, as you've found, in practice if you don't keep sending Cache-Control, browsers will ignore the cache directives that you sent originally, and revert to their own default heuristics.
从理论上讲，您不必为 304 发送 Cache-Control —— 接收者应该继续使用它从原始 200 接收到的缓存指令。但是，正如您所发现的，实际上，如果您不这样做继续发送 Cache-Control，浏览器将忽略您最初发送的缓存指令，并恢复到他们自己的默认启发式。
So in practice, you should include the same Cache-Control with a 304 that you would with a 200. The spec only mandates that you send it for a 304 if it's different than what you sent previously (see 10.3.5 304 Not Modified) -- but it certainly doesn't forbid you from repeating it when it's the same.
因此，在实践中，您应该使用 304 包含与使用 200 相同的 Cache-Control。规范仅要求您将其发送为 304，如果它与您之前发送的不同（请参阅10.3.5 304 Not Modified） -- 但它当然不会禁止你在相同的情况下重复它。
And to respond specifically to the wrong-headed points from the other answer (Structure's):
并专门回应另一个答案（结构）中错误的观点：
You dowant intermediary caches to cache the response (that is, update their cache entry for the resource). They will respond appropriately to requests from clients with a 200 or a 304, depending on whether the client included a conditional header like If-Modified-Since.
The 120-second ttl willbe refreshed by the 304 (so the same client shouldn't make another request for the same resource for at least another 120 seconds). And clients, as long as they've still got the content cached, willcontinue to make conditional requests for the resource, which you can continue to respond to with a 304.
您确实希望中间缓存缓存响应（即更新资源的缓存条目）。它们将根据客户端是否包含条件标头（如 If-Modified-Since）以 200 或 304 响应来自客户端的请求。
120 秒的 ttl将被 304 刷新（因此同一客户端不应再对同一资源发出至少 120 秒的另一个请求）。并且客户端，只要他们仍然缓存了内容，就会继续对资源发出有条件的请求，您可以继续使用 304 进行响应。
回答by Mark Nottingham
RFC7232updates RFC2616 to say:
RFC7232更新 RFC2616 说：
The server generating a 304 response MUST generate any of the following header fields that would have been sent in a 200 (OK) response to the same request: Cache-Control, Content-Location, Date, ETag, Expires, and Vary.
生成 304 响应的服务器必须生成以下任何可能在 200（OK）响应中发送到同一请求的头字段：Cache-Control、Content-Location、Date、ETag、Expires 和 Vary。
回答by Structure
If I understand correctly then the browser is in fact caching for 120 seconds and your server is responding 304 Not Modified to subsequent If-Modified-Since requests. This "IMS" request occurs when the end-user accesses the same URL. At that time the browser can send an If-Modified-Since request. The browser wants to know if it is displaying stale content. This seems normal.
如果我理解正确，那么浏览器实际上缓存了 120 秒，并且您的服务器正在响应 304 Not Modified 到后续 If-Modified-Since 请求。当最终用户访问相同的 URL 时，会发生此“IMS”请求。那时浏览器可以发送 If-Modified-Since 请求。浏览器想知道它是否显示过时的内容。这似乎很正常。
Upon receiving this request your server should reply 200 OK, 304 Not Modified (or a 4XX, if necessary).
收到此请求后，您的服务器应回复 200 OK, 304 Not Modified（或 4XX，如有必要）。
I do not believe you should set your server to send a Cache-Control header with the 304 response for two reasons:
1. You do not want any intermediary caches to cache that 304 response (there is a possibility that they could)
2. The 120 second TTL will not be refreshed by the 304 response. The browser will retain the object for 120 seconds from the 200 OK response. After 120 seconds the browser shouldsend a GET request, not an If-Modified-Since, so your server will respond with the bytes of the file and not just a 304 response.
我认为您不应该将您的服务器设置为发送带有 304 响应的 Cache-Control 标头，原因有两个：
1. 您不希望任何中间缓存缓存该 304 响应（它们有可能）
2. 304 响应不会刷新 120 秒 TTL。从 200 OK 响应开始，浏览器将保留该对象 120 秒。120 秒后，浏览器应该发送 GET 请求，而不是 If-Modified-Since，因此您的服务器将使用文件的字节进行响应，而不仅仅是 304 响应。
Note that the browser will not request the file again automatically after 120 seconds unless the end-user specifically requests it via a page load or directly inputting the URL into their address bar (or unless you have a custom application that controls that functionality somehow).
请注意，浏览器不会在 120 秒后自动再次请求文件，除非最终用户通过页面加载或直接将 URL 输入地址栏中明确请求（或者除非您有一个以某种方式控制该功能的自定义应用程序）。
Edited the first paragraph to read a bit better(hopefully)
编辑了第一段以更好地阅读（希望如此）
