Railey Diesel Age - Brightlocal News
Ok, even if you aren't using express, what essentially needed is to set the nocache headers. I'm adding the headers in a reusable middleware, otherwise you can set those headers in any way that works. The list is just examples of different techniques, it's not for direct insertion.
I don't find get the practical difference between cache-control:no-store and cache-control:no-cache. As far as i know, no-store means that no cache device is allowed to cache that response. Our investigations have shown us that not all browsers respect the http cache directives in a uniform manner. For security reasons we do not want certain pages in our application to be cached, eve I want to ensure that data i request via an ajax call is fresh and not cached. Therefor i send the header cache-control: No-cache but my chrome version 33 overrides this header with cache-control:
I want to ensure that data i request via an ajax call is fresh and not cached. Therefor i send the header cache-control: No-cache but my chrome version 33 overrides this header with cache-control: Beware of etag even if you are using nocache, the etag header isn't removed, because it works in a different way. It's generated at the end of the request and could be another source of unintended …
