Ralph, you're being obtuse on this topic...
Yes, there is a large concern about information leaking out or being compromised.
I spoke with a developer today and this is what he told me with some degree of certainty...
Apparently the .Net app has a way to send messages to IE8 telling it "Do not cache any photographs".
He was unsure if the app can physically flush any pictures that may already be in cache.
And he was unsure what can and cannot be done with other browsers.
I have heard of the ability to do this before with IE.
I thought there was a way to tell all browsers "Do not cache the web page or any photos", but I'm not sure how easily the user can over-ride that. (My guess, is that such an approach probably isn't very secure or fool-proof?!)
Because the project I am working on is a "Test Bank" which contains images that can contain testing content, they are very very concerned about controlling information.
I can see it being a problem if a user's browser cached a whole bunch of images and then they fell into the wrong hands.
Not being an architect, I'm not sure what the way to address this problem is?! :-/
[b]The best thing I can point to is, "How do banks that offer online-banking address this issue?"
For instance, if you look at images of cancelled checks or possibly bank statements, what would your bank do to make sure there there isn't a bread-crumb trail left behind for anyone accessing your computer or browser's cache?[/b]
(This is one of many reason I do NOT bank online!!!)
I wonder if someone like Paul O' knows about this?
Too bad DeathShadow isn't around here anymore...