Once the shopper receives to some page by hitting the again button, how to really make it load a contemporary copy in place of cached just one? 3
On second imagined I discourage all to make use of ClearHeaders strategy. It is really much better to remove headers separately. And also to established Cache-Control header properly I'm using this code:
Business technical concerns lead to unsuccessful payment becoming considered profitable. Do I have any duty to notify?
On IE6, and Opera 9-10, hitting the again button however caused the cached version being loaded. On all other browsers I tested, they did fetch a refreshing version from the server.
So to be able to solution the question, "To cache or never to cache?", you will need to balance your bandwidth and server capabilities (and your willingness to potentially max them out) against the necessity that you have the absolute freshest bits. In the event you don't have such a requirement, then no-cache may be overkill.
The PHP documentation for your header perform features a instead full case in point (contributed by a third party):
Is it impolite to make a person an instructional reference without receiving their permission first? more incredibly hot questions
Request for Proposal Rating additional points with your team and take the first phase in scheduling an epic sporting event in Williamsburg.
A work around would be to established a short-living cookie with a relentless name but a GUID value to make the illusion of an "authentication token". A max-age of 1 second is ample (tested in 136 and 137 thus far). A Java Servlet based case in point are available here.
with this solution again click on is allow on every page and disable only soon after logout on Each and every page to the same browser.
I have not been able to verify this, but I'm concerned that my data could be acquiring cached. I only want the caching to be applied to particular actions, not for all actions.
In concept, This suggests the browser would even now cache read more the results, just wouldn't use the cached results. Should be more efficient within the shopper to disable caching through reaction headers.
There isn't much you are able to do about these. The good news is that they commonly cache for shorter time frames, like seconds or minutes.
1 The solutions here are all unhappy. I might add my very own, but This really is shut. According to MDN: developer.mozilla.org/en-US/docs/World wide web/HTTP/Headers/Cache-Control you need to do in truth most likely desire to use as within the question.