· The JavaScript. Note that before we make the AJAX request, we check the cache object to see if we've saved this key's (the key, in this case, is the username because it is unique) information. If so, avoid the repetitive AJAX request and simply return the cached information. If the key does not exist, make the AJAX request and save the result Reviews: · From the topfind247.co docs: By default, requests are always issued, but the browser may serve results out of its cache. To disallow use of the cached results, set cache to false. To cause the request to report failure if the asset has not been modified since the last request, set ifModified to true. However, neither of these address forcing topfind247.cos: 3. · Sometimes, JavaScript modification doesn’t reflect on the page while running the need to clear browser cache manually each time when the file gets updated. It makes the debugging process hard. If the project contains some bug and you fix it but the user needs to clear the browser cache to reflect the changes.
IIS No-Cache. When you need to disable caching for a Controller or Json/View/ActionResult, we're normally instructed to use the [OutputCache] attribute. Keep in mind however, that the [OutputCache] attribute only applies to IIS's cache settings, NOT the browser's cache settings. So, depending on what your needs are, this may not solve. And in order to disable all caching by the browser we can do the following, $.ajaxSetup({cache: false}}); This will have to be placed on top of the script in order for it to work. Javascript. The reason why browsers are able to cache a particular document is due to the url being passed to the browser are identical. Doing this, the browser will never cache the static files declared in your topfind247.cor example (because will always received a Moved Temporarily), but will only cache the ones with the hash version (the server will answer for them). So the browser cache will be used efficiently for those static files with hash version.
Internet Explorer is one of the browsers that tries to maximize its caching ability. If you have Ajax incorporated into your web site, this may be an issue for users that access your website using a browser configured to cache information from the web server. To prevent the browser from caching, you have several options. Sometimes, JavaScript modification doesn’t reflect on the page while running the need to clear browser cache manually each time when the file gets updated. It makes the debugging process hard. If the project contains some bug and you fix it but the user needs to clear the browser cache to reflect the changes. This is not possible with (only) AJAX. There are two main techniques you could use here, both without using JavaScript to perform the actual download. The general idea is that you redirect the browser to a resource that will provide the desired document; if you're redirecting to a download it will not leave the page but show the Save dialog.
0コメント