: Can I expect browsers to cache static content served over SSL encryption? With all the talk about FireSheep I am thinking of switching my web applications to use full https accross the entire
With all the talk about FireSheep I am thinking of switching my web applications to use full https accross the entire site. However, I am concerned about caching. I use a lot of JavaScript, CSS files, images, and other static content that I expect the browser to cache. If it doesn't that could mean significant delays for users.
Is there a way to get browsers to cache static content served via SSL? Will the cache-control: public HTTP header help? How do the different browsers handle this? Do they never cache the data? Do they cache for a single browser session?
I don't want to serve the static content from an unsecured connection if that means some browsers will put up the warning that some resources are not secure. Is there an alternative solution?
Thanks!
More posts by @Vandalay111
1 Comments
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.