Re: Preventng cacheing

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 30695
interpreted = N
texte = >We have a business issue for a product in the early Requirements Analysis >phase that requires no trace of any web session remain on the user's >computer; read that, the system does not cache any pages, no cookies, etc.This is impossible. You're wasting your time if you think there is any way to prevent a visitor from storing the data your server sends him via http. Once it's on his computer, he gets to keep it -- forever if that's what he wants -- and there is nothing you can do about it. >Does anyone have any ideas in this area, and/or have you experience doing >this?Even if you could force a browser to *not* cache files it receives, the visitor still has the option to save every page as source, or to view the source then copy and paste it into a text file. And image files can always be cached. Like I said, you're wasting your time.You need a proprietary client-sever solution, not the web.================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Associated Messages, from the most recent to the oldest:

    
  1. Re: Preventng cacheing (Kenneth Grome 2000)
  2. Preventng cacheing (Larry Hewitt 2000)
>We have a business issue for a product in the early Requirements Analysis >phase that requires no trace of any web session remain on the user's >computer; read that, the system does not cache any pages, no cookies, etc.This is impossible. You're wasting your time if you think there is any way to prevent a visitor from storing the data your server sends him via http. Once it's on his computer, he gets to keep it -- forever if that's what he wants -- and there is nothing you can do about it. >Does anyone have any ideas in this area, and/or have you experience doing >this?Even if you could force a browser to *not* cache files it receives, the visitor still has the option to save every page as source, or to view the source then copy and paste it into a text file. And image files can always be cached. Like I said, you're wasting your time.You need a proprietary client-sever solution, not the web.================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Kenneth Grome

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[WebDNA] DNA suffix (2008) how does multiple [cart] commands work? (2007) anyone interested in doing an open-source WebCat basedforum? (2002) Ampersand Searching (2000) Separate SSL Server (1997) Edit Plus and webcat code library - Gary Krockover (2003) Still can't upgrade users.db to 2.1.1 (1998) Location of Webcat site in folder hierarchy (1997) Slightly OT: [sendmail] help (2003) [WebDNA] users.db (2009) b12 cannot limit records returned and more. (1997) Re1000001: Setting up shop (1997) Emailer Error Question (1998) WC2.0 Memory Requirements (1997) Grepping URL-Encoded Text (2004) How big can WebCat go? (1999) OFF-TOPIC: Check www.godaddy.com for me ... (2003) Sorting by multiple fields (2003) F3 crashing server (1997) WebCat2b12--[searchstring] bug (1997)