304：不满足使用 HTTP 条件标头指定的条件
我目前正在 Azure Blob 存储中存储文件，当我请求文件时，我在 firebug 中收到一条消息 304“未满足使用 HTTP 条件标头指定的条件”
我查看了 Azure Blob：“使用 HTTP 条件指定的条件header(s) is not met" 及其类似的问题，但我没有阅读使用 blob.openread 等的内容...我只是尝试在浏览器中查看内容。
如果我在 Firefox 中执行控件刷新（ctrl 和 f5），我会得到 200 的响应 - 所以它被正确提供。我已经在返回的文件上设置了缓存控制（max-age=3600，公共），但仍然收到此错误/通知。
我的问题是，当我请求内容时，我是否应该担心它会返回此响应？
您的任何建议/想法都会受到极大的欢迎，
谢谢 史蒂夫
I'm currently storing files within Azure Blob Storage and when I request the files I get an message in firebug of 304 “The condition specified using HTTP conditional header(s) is not met”
I've looked at Azure Blob: "The condition specified using HTTP conditional header(s) is not met" and its a similar question but I'm not reading the content in using blob.openread etc... I'm just trying to view the content in a browser.
If I do a control refresh (ctrl and f5) in firefox I get a response of 200 - so its being served out correctly. I've set the cache control (max-age=3600, public) on the file I'm returning but yet I still get this error / notification.
My question is, should I be worried that when I request the content that its coming back with this response?
Any advice / thoughts you have will be greatly received
Thanks
Steve
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果自浏览器上次访问内容以来 Blob 存储中的内容未发生更改，那么这是正确的行为。
HTTP 状态代码 304 定义为“未修改”（请参阅 http://www. w3.org/Protocols/rfc2616/rfc2616-sec10.html）。我预计您的浏览器已将上次收到的 ETag 与内容一起发送到 HTTP If-None-Match 标头中的 Blob 存储，并且由于此 ETag 仍然与与存储中的内容关联的 ETag 匹配，因此无需发送一个新版本。
有关 ETag 的更多信息，请访问：http://en.wikipedia.org/wiki/HTTP_ETag。您可以通过 Fiddler 查看此行为的实际效果。
FireFox Ctrl-F5 显式强制刷新，这意味着不会发送 If-None-Match 标头。因此，Blob 存储会通过网络发送图像的新副本。
If the content in Blob Storage hasn't changed since your browser last accessed the content then this is the correct behaviour.
HTTP status code 304 is defined as "Not Modified" (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html). What I would anticipate is that your browser has sent the ETag which it last received with the content to Blob Storage in the HTTP If-None-Match header, and as this ETag still matches the ETag associated with the content in storage there's no need to send a new version down the wire.
More on ETags here: http://en.wikipedia.org/wiki/HTTP_ETag. You can see this behaviour in action through Fiddler.
The FireFox Ctrl-F5 explicitly forces a refresh, which means that no If-None-Match header is sent. Blob Storage therefore sends a fresh copy of the image down the wire.