HTTP1.1中启用Cache-Control 来控制页面的缓存与否，这里介绍几个常用的参数： no-cache，浏览器和缓存服务器都不应该缓存页面信息； public，浏览器和缓存服务器都可以缓存页面信息； no-store
when a page is CSR fallback, the CSR app is served with the Cache-Control:no-store header to ensure it...when a page is CSR fallback, the CSR app is served with the Cache-Control:no-store header to ensure it...In this case, the response does not have Cache-Control: no-store in the header....Cache-Control: no-store is only there in CSR fallback case. 更多Jerry的原创文章，尽在：“汪子熙”:
HTTP/1.1 500 X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store...Pragma: no-cache Expires: 0 X-Frame-Options: DENY X-Application-Context: application Cache-Control: no-store...Pragma: no-cache Expires: 0 X-Frame-Options: DENY X-Application-Context: application Cache-Control: no-store...Pragma: no-cache Expires: 0 X-Frame-Options: DENY X-Application-Context: application Cache-Control: no-store...Pragma: no-cache Expires: 0 X-Frame-Options: DENY X-Application-Context: application Cache-Control: no-store
HTTP/1.1 400 X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store...Pragma: no-cache Expires: 0 X-Frame-Options: DENY X-Application-Context: application Cache-Control: no-store...HTTP/1.1 200 X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store...Pragma: no-cache Expires: 0 X-Frame-Options: DENY X-Application-Context: application Cache-Control: no-store...Pragma: no-cache Expires: 0 X-Frame-Options: DENY X-Application-Context: application Cache-Control: no-store
HTTP/1.1 401 X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store..., max-age=0, must-revalidate Pragma: no-cache Expires: 0 X-Frame-Options: DENY Cache-Control: no-store...HTTP/1.1 200 X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store...HTTP/1.1 403 X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store...Pragma: no-cache Expires: 0 X-Frame-Options: DENY X-Application-Context: application Cache-Control: no-store
（3）需要后端陪着，进行 nginx 配置 location = /index.html { add_header Cache-Control "no-cache, no-store..."; } 原因： 第二种方法浏览器也会出现缓存，配置之后禁止html 出现缓存 no-cache, no-store可以只设置一个 no-cache浏览器会缓存，但刷新页面或者重新打开时 会请求服务器，...服务器可以响应304，如果文件有改动就会响应200 no-store浏览器不缓存，刷新页面需要重新下载页面 （4）在脚本加载时加入一个时间戳，修改 webpack.prod.conf.js 文件。
用户将输入的代码、用户应访问的 URL 和轮询间隔的 JSON 负载进行响应 HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store...HTTP/1.1 400 Bad Request Content-Type: application/json Cache-Control: no-store { "error": "slow_down...HTTP/1.1 400 Bad Request Content-Type: application/json Cache-Control: no-store { "error": "access_denied...HTTP/1.1 400 Bad Request Content-Type: application/json Cache-Control: no-store { "error": "expired_token...HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store { "access_token": "AYjcyMzY3ZDhiNmJkNTY
这需要在服务器配置不让缓存index.html nginx配置，让index.html不缓存 location = /index.html { add_headerCache-Control"no-cache,no-store..."; } no-cache,no-store可以只设置一个 no-cache浏览器会缓存，但刷新页面或者重新打开时会请求服务器，服务器可以响应304，如果文件有改动就会响应200 no-store浏览器不缓存
前端设置html页面缓存方法：静态的html页面想要设置使用缓存需要通过HTTP的META设置expires和cache-control 解决问题 cache-control：||no-cache||no-store...中我们设置了no-cache之后，请求虽然不会直接使用缓存，但是还会用缓存数据与服务器数据进行一致性检测(也就是说还是有几率会用到缓存的), firefox中则完全无视no-cache存在，详细解释见no-store...; 2，no-store： 指示缓存不存储此次请求的响应部分。...与no-cache比较来说，一个是不用缓存，一个是不存储缓存;按理来说这个设置更加粗暴直接禁用缓存， 但是具体实现起来 浏览器之间差异却特别大，一般不会直接用该字段进行设置，不过no-store是为了防止缓存被恶意修改存储路径导致信息被泄露而设置的...， 毕竟有它的用处，在firefox中实现缓存是通过文件另存为将缓存副本保存到本地，直接利用no-cache对其是无效的，如果加上no-store设置的话 则可以起到与no-cache一样的效果; 即：
28T21:24:06+08:00] HTTP/1.1 200 OK Connection: close Content-Length: 545 Cache-Control: no-cache, no-store..., max-age=0, must-revalidate Cache-Control: no-store Content-Language: en-US Content-Type: application..., max-age=0, must-revalidate Cache-Control: no-store Content-Type: application/json;charset=UTF-8..., max-age=0, must-revalidate Cache-Control: no-store Content-Type: application/json;charset=UTF-8..., max-age=0, must-revalidate Cache-Control: no-store Content-Type: application/json;charset=UTF-8
为什么我们有时候设置了<meta http-equiv="Cache-control" content="<em>no-store</em>...try_files $uri $uri/ /index.html; add_header Last-Modified $date_gmt; add_header Cache-Control '<em>no-store</em>...proxy-revalidate, max-age=0'; if_modified_since off; expires off; etag off; } no-cache, <em>no-store</em>...可以只设置一个 no-cache 浏览器会缓存，但刷新页面或者重新打开时 会请求服务器，服务器可以响应 304，如果文件有改动就会响应 200 <em>no-store</em> 浏览器不缓存，刷新页面需要重新下载页面
HTTP/1.1 400 X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store...Pragma: no-cache Expires: 0 X-Frame-Options: DENY X-Application-Context: application Cache-Control: no-store...HTTP/1.1 200 X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store...Pragma: no-cache Expires: 0 X-Frame-Options: DENY X-Application-Context: application Cache-Control: no-store..., max-age=0, must-revalidate Pragma: no-cache Expires: 0 X-Frame-Options: DENY Cache-Control: no-store
经测试跨浏览器禁止缓存的 headers 如下： Cache-Control: no-cache, no-store, must-revalidate Pragma: no-cache Expires:...for proxies 因为是 HTML 页面，可以于 HEAD 标签内直接添加 META 标签： <meta http-equiv="Cache-Control" content="no-cache, <em>no-store</em>
gzip_min_length length; gzip_min_length 20; http, server, location gzip_proxied off | expired | no-cache | no-store...的值进行比较，只有大于gzip_min_length的响应才会进行压缩，比较合理的值是1000 gzip_proxied 语法：gzip_proxied off | expired | no-cache | no-store...如果响应头包含“Expires”字段，且该字段的值禁止缓存，则启用压缩; no-cache 如果响应头包含带有“ no-cache”参数的“Cache-Control”字段，则启用压缩; no-store... 如果响应头包含带有“ no-store”参数的“Cache-Control”字段，则启用压缩; private 如果响应头包含带有“ private”参数的“Cache-Control
一、请求时想要禁用缓存, 可以设置请求头: Cache-Control: no-cache, no-store, must-revalidate 二、另一种常用做法: 给请求的资源增加一个版本号, 如下...
The CSR app (index.html) is served with a Cache-Control:no-store header....这个 index.html 返回时带有 Cache-Control:no-store 头部。 As a result, it is not stored by the cache layer....服务器端页面不包含 Cache-Control:no-store 头部字段，因为 SSR 渲染好的页面需要被缓存。
使用范例 gzip on; gzip_min_length 1000; gzip_proxied expired no-cache no-store private auth; gzip_types...gzip_proxied 语法: gzip_proxied [off|expired|no-cache|no-store|private|no_last_modified|no_etag|auth|any...expired – 启用压缩，如果header头中包含 “Expires” 头信息 no-cache – 启用压缩，如果header头中包含 “Cache-Control:no-cache” 头信息 no-store...– 启用压缩，如果header头中包含 “Cache-Control:no-store” 头信息 private – 启用压缩，如果header头中包含 “Cache-Control:private
expired：如果响应头包含“Expires”字段，其值为禁用缓存，则启用压缩; no-cache：如果响应头包含带有“ no-cache”参数的“Cache-Control”字段，则启用压缩; no-store...：如果响应头包含带有“ no-store”参数的“Cache-Control”字段，则启用压缩; private：如果响应头包含带有“ private”参数的“Cache-Control”字段，则启用压缩
200 OK Content-Type: text/plain Date: Sat, 13 Nov 2021 05:08:00 GMT Server: Kestrel Cache-Control: no-store...200 OK Content-Type: text/plain Date: Sat, 13 Nov 2021 05:08:00 GMT Server: Kestrel Cache-Control: no-store...200 OK Content-Type: text/plain Date: Sat, 13 Nov 2021 05:14:05 GMT Server: Kestrel Cache-Control: no-store...1.1 299 Content-Type: text/plain Date: Sat, 13 Nov 2021 05:19:34 GMT Server: Kestrel Cache-Control: no-store...1.1 298 Content-Type: text/plain Date: Sat, 13 Nov 2021 05:19:30 GMT Server: Kestrel Cache-Control: no-store
<meta http-equiv="cache-control" content="no-cache, <em>no-store</em>...:htm|html)$) { add_header Cache-Control "no-cache, no-store"; //对html文件设置永远不缓存...} } } no-cache浏览器会缓存，但刷新页面或者重新打开时 会请求服务器，服务器可以响应304，如果文件有改动就会响应200 no-store浏览器不缓存，刷新页面需要重新下载页面 三
领取专属 10元无门槛券
手把手带您无忧上云
云服务器
即时通信 IM
ICP备案
对象存储
实时音视频
