Meta setting cache-control invalidation
problem description
set cache-control in the meta tag in the html file, but the relevant cache-control is not returned in the response header
the environmental background of the problems and what methods you have tried
tried pragma, too.
what result do you expect?
you want to request the server directly without reading the browser cache. Is an a tag this page jumps to the target page, which needs to directly request the server without caching.
only front-end operations. It is not clear whether the server needs to perform certain operations. If necessary, please help us to analyze Thanks operations () operations in detail
.
have the server set cache-control: no-store for this file
the configuration at the front end is only a product of history, and now it has basically been eliminated
. In terms of browsers, it is very simple. This is only a private attribute of the IE era, which was supported before IE9, but now the mainstream chrome\ firefox\ safari, including IE9-11, is no longer supported. If the application needs to be compatible with low-version IE browsers (such as banks, zf, etc.), you can add this thing. Otherwise, it won't be necessary at all.
in terms of http, this is a product of the http1.0 era, because there is so little about caching in http1.0 (you know, http0.9 simply does not support server-side response.header,http1.0, although it adds header, but there is not much that can be set except status code), and in the early days of http1.1 release, not all browsers support it, so the cache-control that controls caching is put into the front-end html page.
currently, this configuration should take effect only in the file:// protocol
https://blog.csdn.net/u598975767/article/details/113091716
