Edward BreyEdward Brey forty one.9k2121 gold badges212212 silver badges268268 bronze badges one Unfortunately this does not look to work, as hitting the back button after a sign out displays the page.

For what it's worth, I just needed to handle this in my ASP.Internet MVC 3 software. Here may be the code block I used while in the Global.asax file to handle this for all requests.

One particular solution will be to pass a timestamp to guarantee ie thinks it's a different http service request. That worked for me, so including a server side scripting code snippet to automatically update this tag would not harm:

Note: any time you set NoStore Duration parameter isn't considered. It is achievable to established an initial duration for first registration and override this with custom attributes.

So so as to respond to the question, "To cache or to not cache?", you will need to balance your bandwidth and server abilities (and your willingness to potentially max them out) against the necessity that you have absolutely the freshest bits. Should you don't have this type of requirement, then no-cache might be overkill.

Our prerequisite arrived from a safety test. After logging out from our website you may press the again button read more and look at cached pages.

I'd no luck with components. Including HTTP cache linked parameters directly (outside of the HTML doc) does certainly work for me.

Why would be the number of Marie Curie postdoctoral fellowships in mathematics significantly lower than in other topics?

seven Never install this deal to avoid wasting four lines of code. Minimizing dependencies ought to often be considered one of your aims. Every dependency you add is another matter that needs to be updated, another method of getting your project hacked, another method to insert even more dependencies if this deal adds dependencies, and many others.

with this Alternative again simply click is enable on every page and disable only soon after logout on Each individual page around the same browser.

Remember that it can be extremely hard to force the browser to disable caching. The best you can do is deliver solutions that most browsers will honor, normally during the form of headers or meta tags.

In case you are an experienced developer is your choice to make a choice from a dependency and code - I incorporated every one of the headers in my answer Because of this. FYI: maybe nocache has become the number of npm libraries without dependencies and its writer is a safety expert.

I edited configuration file of my project to append no-cache headers, but that also disabled caching static written content, which is just not usually desirable.

This is often producing a dilemma to my login system (buyers not logged in can open outdated cached pages of logged in consumers).