In the future, you'll probably want to ask a question like this in one
newsgroup at a time, since it's unclear how many replies you've already
gotten for this question.
This is pretty lame, eh? See
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/s
upport/kb/articles/q316/4/31.asp&NoWebContent=1
This refers to SSL delivered documents, but I don't know of any reason this
would only affect SSL.
It's unclear what threats you're trying to mitigate here. Can you
elaborate?

Signature
Thanks,
Eric Lawrence
Program Manager
Assistance and Worldwide Services
This posting is provided "AS IS" with no warranties, and confers no rights.
> Hi,
>
[quoted text clipped - 57 lines]
> Thanks
> Jonathan
Jonathan Trevor - 23 Feb 2004 18:44 GMT
Thanks for the pointer.
We're trying to avoid a user leaving copies of private documents on public
machines by accident. Clearly to do this really well you'd need some digital
rights type support (+encryption) or requiring a "trusted" viewer for
documents on that machine which you can guarantee won't leave a copy
anywhere. However, it seemed that setting "no-cache" would be a good way to
allow documents to be viewed on the machine which would then not be
available after the user had left it. If the user made the choice to
download it and then leaves it, then fine (but not good :-) )
While I understand that a temporary file must be created for ppt (etc) to
open (although what they do with webdav is more interesting) I'm not sure
why IE couldn't open powerpoint, and then cleanup after ppt exits -
presumably it does the same for itself when opening large files it can host
(like jpgs which open directly in IE). Even more annoyingly there is no way
to determine what behavior to expect from different browsers/clients - it
depends on what applications are installed, how they integrate with IE, and
even what versions are installed. For example, clicking "open" on some
machines causes powerpoint to launch and on others causes IE to host the
powerpoint document.
Finally, I'm not convinced the behavior is consistent as the "Save As"
choice will fail on the "SaveAs/Open" dialog - but if you right click on the
document link and click "Save as" from the menu then it saves without
problems!
Basically, I'd like some consistent behavior when the user clicks on
"Download this document" - i.e. it should never fail wierdly (such as "Save
As" or "Open" failures).
Jonathan
> In the future, you'll probably want to ask a question like this in one
> newsgroup at a time, since it's unclear how many replies you've already
> gotten for this question.
>
> This is pretty lame, eh? See
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/s
upport/kb/articles/q316/4/31.asp&NoWebContent=1
> This refers to SSL delivered documents, but I don't know of any reason this
> would only affect SSL.
[quoted text clipped - 68 lines]
> > Thanks
> > Jonathan