Proxies aren't necessarily going to read the contents of the HTML document and parse
the META tags. META is really intended just for the browser. Good proxies should,
however, pay attention to real HTTP headers such as those set by CFHEADER.
As to the original question, I think something like the following might help. User
hits Log Off, a page is returned which has a JS or META redirect on it that points to
some other page. When user hits Back, they're taken to the page with the redirect,
which then sends them back to the page they were just on. Unfortunately this doesn't
really help if they go Back 2 or more pages (via IE's dropdown Back button, for
example) :( The surest way to keep 'em out is make sure they're still logged in
before they can take any further action (after they back up).
Cheers,
-Max
At 11/2/2000 10:08 AM -0500, you wrote:
>Well, this is what I use (be sure to put it in the <HEAD> element). It meets HTML
>standards, but I'm having trouble with some caching proxies that seem to ignore any
>no-cache commands.
>
><meta http-equiv="pragma" content="no-cache">
><meta http-equiv="expires" content="Mon, 01 Jan 1990 12:34:56 GMT">
>
>Chris Norloff
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
