Upgrade your Nginx. Syntax: etag on | off; Default: etag on; Context: http, server, location This directive appeared in version 1.3.3. Enables or disables automatic generation of the “ETag” response header field for static resources. Source: http://nginx.org/en/docs/http/ngx_http_core_module.html#etag
There are two things to consider when dealing with cache in Express.js – ETag and Cache-Control headers. ETag (MDN reference) If you have dynamic content which does not benefit from ETags, it’s best to disable it because it incurs small overhead with each request. app.set(‘etag’, false) Cache-Control (MDN reference) To completely disable cache, use the … Read more
I have found a quite elegant way: It is enough to set: CKEDITOR.timestamp=’ABCD’; just after you link ckeditor.js or anyhow before ckeditor loads all its files this is the variable CKEDITOR uses to add timestamp to all .js .css files it loads dynamically. So every time I change those files I update that variable and … Read more
This issue occurs if the server sends a “Cache-control:no-store” header or sends a “Cache-control:no-cache” header.
I had the same problem and changing (incrementing) the version number in package.json before running the build command fixed it. For example by default the version number is set to “0.1.0” package.json file: { “name”: “project-name”, “version”: “0.1.1”, “private”: true, … }
How are you defining your require.config? I think for it to take effect before you import require.js, you need to code it like this: <script type=”text/javascript”> var require = { baseUrl: “/scripts/”, waitSeconds: 15, urlArgs : “bust=”+new Date().getTime() }; </script> <script data-main=”app/main” src=”https://stackoverflow.com/scripts/require.js”></script> Specifically, a an object named ‘require’ must be constructed before you import … Read more
I’ve eventually figured it out. Here is an explanation and a tested solution. The following site confirms my observation: http://blog.httpwatch.com/2008/10/15/two-important-differences-between-firefox-and-ie-caching/ It says that IE does not locally store pages with the ‘no-cache’ directive and hence always sends an unconditional request. There’s also a MS support article – https://support.microsoft.com/help/234067/ – which confirms this: “Internet Explorer supports … Read more
If you would like to achieve cache busting in “webpack way”: 1. Hash name of output files Change output filenames to hash generated names (on build phase) output: { path: “https://stackoverflow.com/”, filename: ‘[hash].js’, chunkFilename: ‘[chunkhash].js’, }, From that point your foo.js and chunk.1.js will be called like e883ce503b831d4dde09.js and f900ab84da3ad9bd39cc.js. Worth mention that generation of … Read more
It shouldn’t be cached at all unless there’s also a Cache-Control or Expires header returned by the web server. According to RFC 2616, section 10.3.3 302 Found The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. … Read more
I have limited experience, but for what I can understand: Cache is data which is used very frequently, so it is stored to reduce processing and loading required. In a computer, the cache is what helps to hold temporary data used by the processor to compute the most basic instructions. It is a lot faster, … Read more