http - What are the drawbacks of using cache-control: no-store? -


we want "prevent inadvertent release or retention of sensitive information (for example, on backup tapes :) )" , plan use http header cache-control: no-store. down-sides of doing so? spec, appears caching continue operate - cannot use non-volatile storage. in order choose responses specify no-store on, have measure of "sensitivity." counterbalancing measure we should use - in other words, why not mark pages no-store?

by using store, client has local cache can use. cache gives them performance boost , decreases load on own server.

in case, think makes sense have sensitive pages sent no caching.

i believe technical problem no-store (and more of weird side effect) older versions of ie have problems content-disposition header caching turned off. behavior such download prompt indefinitely have 0% progress.

one misconception no-caching policies browser honor , not save disk. not true - many modern browsers cache responses disk (see so). however, cache is encrypted in cases.

overall, think safe so. make sure you're not relying on mechanism @robert harvy says, once send over, you're @ mercy of browser of how wants save it.


Comments

Popular posts from this blog

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -

Trying to import CSV file to a SQL Server database using asp.net and c# - can't find what I'm missing -